Viewing Basic Cluster Information

Updated on 2024-12-19 GMT+08:00

View PDF

You can monitor and manage the clusters you have created. Choose Clusters > Active Clusters. Select a cluster and click its name to go to the cluster details page. On the displayed page, view the basic configuration and node information of the cluster.

On the cluster details page, click Dashboard. Table 1, Table 2, Table 3, and Table 4 describe the parameters on the Dashboard tab page.

**Table 1** Basic information
Parameter	Description
Cluster Name	The name of a cluster. Configure this parameter when creating a cluster. Click to change the cluster name.
Cluster Status	The cluster status. For details, see Table 1.
Cluster Version	MRS version information.
Cluster Type	There are three types of clusters: Analysis Cluster: is used for offline data analysis and provides Hadoop components. Streaming Cluster: is used for streaming tasks and provides stream processing components. Hybrid Cluster: is used for both offline data analysis and streaming processing and provides Hadoop components and streaming processing components. Custom: An MRS cluster with all custom components.
Cluster ID	Unique identifier of a cluster, which is automatically assigned when a cluster is created.
Created	Time when a cluster is created.
AZ	Availability zone (AZ) in the region of a cluster, which is set when a cluster is created.
Kerberos Authentication	Whether to enable Kerberos authentication when logging in to Manager.
Enterprise Project	The enterprise project to which a cluster belongs. Only on the Active Clusters page, you can click the name of an enterprise project to go to its Enterprise Project Management page.

**Table 2** Network information
Parameter	Description
Default Subnet	The subnet selected during cluster creation. If the subnet IP addresses are insufficient, click Change Subnet to switch to another subnet in the same VPC of the current cluster to obtain more available subnet IP addresses. Changing a subnet does not affect the IP addresses and subnets of existing nodes. A subnet provides dedicated network resources that are isolated from other networks, improving network security.
VPC	VPC selected during cluster creation. A VPC is a secure, isolated, and logical network environment.
EIP	After binding an EIP to an MRS cluster, you can use the EIP to access the Manager web UI of the cluster. If you do not need the EIP, click Unbind to unbind the EIP from the cluster. The Manager will not be accessible through the unbound EIP. NOTE: If you unbind the EIP from a cluster, other users may fail to access the Manager of that cluster.
Security Group	The security group name of the cluster.

**Table 3** O&M management
Parameter	Description
MRS Manager	Portal for the Manager page. see Accessing FusionInsight Manager.
IAM User Sync	IAM user information (including federated users) can be synchronized to an MRS cluster for cluster management. For details, see Synchronizing IAM Users to MRS. NOTE: The Components, Tenants, and Backups & Restorations tab pages on the cluster details page can be used only after users are synchronized. For a federated user, only information about the user that logged in the system can be synchronized.
Data Connection	Click Manage to view the data connection type associated with the cluster. For details, see Configuring Data Connections.
Agency	Click Manage Agency to bind or modify an agency for the cluster. An agency allows ECS or BMS to manage MRS resources. You can configure an agency of the ECS type to automatically obtain the AK/SK to access OBS. For details, see Configuring a Storage-Compute Decoupled Cluster (Agency). The MRS_ECS_DEFAULT_AGENCY agency has the OBS OperateAccess permission of OBS and the CES FullAccess (for users who have enabled fine-grained policies), CES Administrator, and KMS Administrator permissions in the region where the cluster is located.
OBS Permission Control	Click Manage and modify the mapping between MRS users and OBS permissions. For details, see Configuring Fine-Grained Permissions for MRS Multi-User Access to OBS.
Logging	Used to collect logs about cluster creation and scaling failures.
Secure Communications	Used to display the security authorization status. You can click to enable or disable security authorization. Disabling security authorization brings high risks. Exercise caution when performing this operation. For details, see Communication Security Authorization.

On the cluster details page, click Nodes. For details about the node parameters, see Table 4.

**Table 4** Node information
Parameter	Description
Configure Task Node	Used to add a Task node. For details, see Adding a Task Node. This operation applies only to the analysis cluster, streaming cluster, and hybrid cluster.
Add Node Group	Used to add node groups. This method applies only to customized clusters. For details, see Adding a Node Group.
Node Group	Node group name.
Node Type	Node type: Master: A Master node in an MRS cluster manages the cluster, assigns MapReduce executable files to Core nodes, traces the execution status of each job, and monitors the DataNode running status. A task node group is a group of nodes where only data roles that do not store data are deployed. The roles include NodeManager, ThriftServer, Thrift1Server, RESTServer, Supervisor, LogViewer, HBaseIndexer, and TagSync. If other roles are deployed in the node group in addition to the preceding roles, the node group is the Core node group. On the Nodes tab page, click next to a node group name to unfold the nodes contained in the node group. Click a node name to remotely log in to the ECS using the password or key pair configured during cluster creation. For details about the parameters, see Managing Components and Monitoring Hosts.
Node Count	Number of nodes in a node group.
Operation	Scale Out: For details, see Scaling Out a Cluster. Scale In: For details, see Scaling In a Cluster. Delete: To delete a node group, ensure that there is no node in the node group. View Roles: You can view information about roles deployed on the node group. This function applies only to custom clusters of 3.x and later.