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 V100R002C60SPC200 Product Description 06

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 pubic functions.

A data node of FusionInsight HD can be DataNode, RegionServer, NodeManager, LoaderServer, 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.

  • FusionInsight HD interworks with the service network through the service plane to provide service channels, data storage and access, task submission, and computing capabilities for enterprise users.
  • FusionInsight HD interworks with the operation and maintenance network through the management plane to provide the management and maintenance functions, especially cluster management and cluster monitoring, configuration, auditing, and user management services for enterprise users.

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 configurations, a FusionInsight HD cluster is networked based on dual planes, as shown in Figure 3-1.

Figure 3-1 Typical Networking of a Standard Configuration

Networking Planning

Based on the number of nodes in the cluster, FusionInsight HD is networked as shown in Table 3-2.

Table 3-2 Networking Planning

Deployment Scheme

Networking Planning

Application Scenario

The management node, control node, and data node are deployed separately. 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.
  • (Recommended) Cluster of which the number of nodes is greater than 200.
  • This scheme requires at least eight nodes.
The management node and control node are deployed integrally and the data node is deployed independently. 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. (Recommended) Cluster of which the number of nodes is greater than or equal to six but smaller than or equal to 200.
The management node, control node, and data node are deployed integrally. 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.
  • Cluster of which the number of nodes is smaller than six.
  • This scheme requires at least three nodes.
NOTE:
This scenario is not recommended.
  • 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.
Translation
Download
Updated: 2019-04-10

Document ID: EDOC1000104139

Views: 5864

Downloads: 64

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