No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Product Description 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Networking Scheme

Networking Scheme

Basic Concepts

The networking scheme of a FusionInsight HD cluster contains three nodes. Information about the three types of nodes is listed in Table 3-1.

Table 3-1 Basic Concepts

Concept

Description

Management Node (MN)

A management node is a node where FusionInsight Manager is installed.

FusionInsight Manager that is the management system of a FusionInsight HD cluster to centrally manage nodes and services deployed in the cluster.

Control Node (CN)

A control node controls and monitors how data nodes store and receive data, and send process status, and provides other public functions.

A control node of FusionInsight HD can be HMaster, HiveServer, ResourceManager, NameNode, JournalNode, SlapdServer, or other components.

Data Node (DN)

A data node executes instructions sent by management nodes, reports task status, stores data, and provides other public functions.

A data node of FusionInsight HD can be DataNode, RegionServer, NodeManager, or other components.

Typical Networking

Huawei FusionInsight HD divides the entire network into two planes: the service plane and management plane. The two planes are physically isolated to ensure security of the service and management networks.

  • The management plane is accessed by the O&M network and is used to manage the cluster and provide the cluster monitoring, configuration, audit, and user management services.
  • The service plane is accessed by the service platform and is used to provide service channels for users or upper-layer users, and provide the data storage, service submitting, and computation functions.

The IP address of the external management network can also be configured on the active and standby management nodes. Users can use the external management network to manage the FusionInsight HD cluster. In typical configuration, a FusionInsight HD cluster is networked based on dual planes.

Figure 3-1 Typical networking of standard configuration

Nodes Deployment Schemes

Deploy the networking based on the number of nodes where the FusionInsight HD cluster is deployed and the information in Table 3-2.

NOTE:

If you need to configure Federation and add n pairs of NameNodes besides the default pair, 2n additional control nodes need to be added. For details about Federation, see Service Operation Guide > Federation.

Table 3-2 FusionInsight HD deployment scheme

Deployment Scheme

Application Scenario

Networking Planning

The management node, control node, and data node are deployed separately.

This scheme requires at least eight nodes.

MN × 2 + CN × 11 + DN × n

(Recommended) Cluster of which the number of Data Nodes is 2000 to 5000.

  • When the number of nodes in a cluster exceeds 200, the nodes in the cluster are distributed to different subnets and the subnets communicate with each other in Layer 3 interconnection mode using core switches. Each subnet has at most 200 nodes. Ensure that the node quantity is balanced on different subnets.
  • When the number of nodes in a cluster below 200, the nodes in the cluster are deployed in the same subnet and the nodes communicate with each other in Layer 2 interconnection mode using aggregation switches.

MN × 2 + CN × 9 + DN × n

(Recommended) Cluster of which the number of Data Nodes is 500 to 2000.

MN × 2 + CN × 5 + DN × n

(Recommended) Cluster of which the number of Data Nodes is 100 to 500.

MN × 2 + CN × 3 + DN × n

(Recommended) Cluster of which the number of Data Nodes is 30 to 100.

The management node and control node are deployed integrally and the data node is deployed independently.

(MN+CN) × 3 + DN × n

(Recommended) Cluster of which the number of Data Nodes is greater than or equal to 3 but smaller than or equal to 30.

The nodes in the cluster are deployed in the same subnet and the nodes communicate with each other in Layer 2 interconnection mode using aggregation switches.

The management node, control node, and data node are deployed integrally.

  • Cluster of which the number of nodes is smaller than six.
  • This scheme requires at least three nodes.
NOTE:

This scenario is not recommended in a production environment or commercial environment:

  • If management, control, and data nodes are deployed integrally, cluster performance and reliability are greatly affected.
  • If the number of nodes meets the requirements, it is recommended that data nodes be deployed independently.
  • If the number of nodes cannot meet the requirements for separate data node deployment but this scenario is required, adopt the dual-plane networking. The traffic of the management network is isolated from that of the service network to prevent excessive data volumes on the service plane, ensuring correct delivery of management operations.

The nodes in the cluster are deployed in the same subnet and the nodes communicate with each other in Layer 2 interconnection mode using aggregation switches.

Download
Updated: 2019-05-17

Document ID: EDOC1100074548

Views: 3087

Downloads: 35

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next