Querying Cluster Details

Function

This API is used to query details about a specified cluster. This API is incompatible with Sahara.

URI

  • Format

    GET /v1.1/{project_id}/cluster_infos/{cluster_id}

  • Parameter description

    Table 1 URI parameter description

    Parameter

    Mandatory

    Description

    project_id

    Yes

    Project ID. For details on how to obtain the project ID, see Obtaining a Project ID.

    cluster_id

    Yes

    Cluster ID

Request

Request parameters

None.

Response

Table 2 Response parameter description

Parameter

Type

Description

clusterId

String

Cluster ID

clusterName

String

Cluster name

masterNodeNum

String

Number of Master nodes deployed in a cluster

coreNodeNum

String

Number of Core nodes deployed in a cluster

totalNodeNum

String

Total number of nodes deployed in a cluster

clusterState

String

Cluster status. Valid values include:

  • starting: The cluster is being started.

  • running: The cluster is running.

  • terminated: The cluster has been terminated.

  • failed: The cluster fails.

  • abnormal: The cluster is abnormal.

  • terminating: The cluster is being terminated.

  • frozen: The cluster has been frozen.

  • scaling-out: The cluster is being scaled out.

  • scaling-in: The cluster is being scaled in.

createAt

String

Cluster creation time, which is a 10-bit timestamp

updateAt

String

Cluster update time, which is a 10-bit timestamp

billingType

String

Cluster billing mode

dataCenter

String

Cluster work region

vpc

String

VPC name

fee

String

Cluster creation fee, which is automatically calculated

hadoopVersion

String

Hadoop version

masterNodeSize

String

Instance specifications of a Master node

coreNodeSize

String

Instance specifications of a Core node

componentList

Array

Component list. For details, see Table 3.

externalIp

String

External IP address

externalAlternateIp

String

Backup external IP address

internalIp

String

Internal IP address

deploymentId

String

Cluster deployment ID

remark

String

Cluster remarks

orderId

String

Cluster creation order ID

azId

String

AZ ID

masterNodeProductId

String

Product ID of a Master node

masterNodeSpecId

String

Specification ID of a Master node

coreNodeProductId

String

Product ID of a Core node

coreNodeSpecId

String

Specification ID of a Core node

azName

String

AZ name

instanceId

String

Instance ID

vnc

String

URI for remotely logging in to an ECS

tenantId

String

Project ID

volumeSize

Integer

Disk storage space

subnetId

String

Subnet ID

subnetName

String

Subnet name

securityGroupsId

String

Security group ID

slaveSecurityGroupsId

String

Security group ID of a non-Master node. Currently, one MRS cluster uses only one security group. Therefore, this field has been discarded. This field returns the same value as securityGroupsId does for compatibility consideration.

bootstrap_scripts

Array

Bootstrap action script information. For more parameter description, see Table 5.

stageDesc

String

Cluster operation progress description.

The cluster installation progress includes:

  • Verifying cluster parameters: Cluster parameters are being verified.

  • Applying for cluster resources: Cluster resources are being applied for.

  • Creating VMs: The VMs are being created.

  • Initializing VMs: The VMs are being initialized.

  • Installing MRS Manager: MRS Manager is being installed.

  • Deploying the cluster: The cluster is being deployed.

  • Cluster installation failed: Failed to install the cluster.

The cluster scale-out progress includes:

  • Preparing for scale-out: Cluster scale-out is being prepared.

  • Creating VMs: The VMs are being created.

  • Initializing VMs: The VMs are being initialized.

  • Adding nodes to the cluster: The nodes are being added to the cluster.

  • Scale-out failed: Failed to scale out the cluster.

The cluster scale-in progress includes:

  • Preparing for scale-in: Cluster scale-in is being prepared.

  • Decommissioning instance: The instance is being decommissioned.

  • Deleting VMs: The VMs are being deleted.

  • Deleting nodes from the cluster: The nodes are being deleted from the cluster.

  • Scale-in failed: Failed to scale in the cluster.

If the cluster installation, scale-out, or scale-in fails, stageDesc will display the failure cause. For details, see Table 8.

mrsManagerFinish

boolean

Whether MRS Manager installation is finished during cluster creation.

  • true: MRS Manager installation is finished.

  • false: MRS Manager installation is not finished.

safeMode

String

Running mode of an MRS cluster

  • 0: Normal cluster

  • 1: Security cluster

clusterVersion

String

Cluster version

nodePublicCertName

String

Name of the public key file

masterNodeIp

String

IP address of a Master node

privateIpFirst

String

Preferred private IP address

errorInfo

String

Error message

tags

Array

Tag information

chargingStartTime

String

Start time of billing

clusterType

String

Cluster type

logCollection

Integer

Whether to collect logs when cluster installation fails

  • 0: Do not collect.

  • 1: Collect.

taskNodeGroups

List<NodeGroup>

List of Task nodes. For more parameter description, see Table 4.

nodeGroups

List<NodeGroup>

List of Master, Core and Task nodes. For more parameter description,

see Table 4.

masterDataVolumeType

String

Data disk storage type of the Master node. Currently, SATA, SAS and SSD are supported.

masterDataVolumeSize

Integer

Data disk storage space of the Master node. To increase data storage capacity, you can add disks at the same time when creating a cluster.

Value range: 100 GB to 32,000 GB

masterDataVolumeCount

Integer

Number of data disks of the Master node.

The value can be set to 1 only.

coreDataVolumeType

String

Data disk storage type of the Core node. Currently, SATA, SAS and SSD are supported.

coreDataVolumeSize

Integer

Data disk storage space of the Core node. To increase data storage capacity, you can add disks at the same time when creating a cluster.

Value range: 100 GB to 32,000 GB

coreDataVolumeCount

Integer

Number of data disks of the Core node.

Value range: 1 to 10

scale

String

Node change status. If this parameter is left blank, the cluster nodes are not changed.

Possible values are as follows:

  • scaling-out: The cluster is being scaled out.

  • scaling-in: The cluster is being scaled in.

  • scaling-error: The cluster is in the running state and fails to be scaled in or out or the specifications fail to be scaled up for the last time.

  • scaling-up: The Master node specifications are being scaled up.

  • scaling_up_first: The standby Master node specifications are being scaled up.

  • scaled_up_first: The standby Master node specifications have been scaled up successfully.

  • scaled-up-success: The Master node specifications have been scaled up successfully.

Table 3 componentList parameter description

Parameter

Type

Description

componentId

String

Component ID

  • Component IDs of MRS 3.2.0-LTS.2 are as follows:

    • MRS 3.2.0-LTS.2_001: Hadoop

    • MRS 3.2.0-LTS.2_002: HBase

    • MRS 3.2.0-LTS.2_003: Hive

    • MRS 3.2.0-LTS.2_004: Spark2x

    • MRS 3.2.0-LTS.2_006: Flink

    • MRS 3.2.0-LTS.2_008: Kafka

    • MRS 3.2.0-LTS.2_009: Flume

    • MRS 3.2.0-LTS.2_013: Loader

    • MRS 3.2.0-LTS.2_014: Hue

    • MRS 3.2.0-LTS.2_015: Ooize

    • MRS 3.2.0-LTS.2_018: DBService

    • MRS 3.2.0-LTS.2_019: ZooKeeper

    • MRS 3.2.0-LTS.2_022: Ranger

    • MRS 3.2.0-LTS.2_023: HetuEngine

    • MRS 3.2.0-LTS.2_024: Tez

    • MRS 3.2.0-LTS.2_025: ClickHouse

    • MRS 3.2.0-LTS.2_026: IoTDB

    • MRS 3.2.0-LTS.2_028: CDL

  • Component IDs of MRS 3.1.2-LTS.6 are as follows:

    • MRS 3.1.2-LTS.6_001: Hadoop

    • MRS 3.1.2-LTS.6_002: HBase

    • MRS 3.1.2-LTS.6_003: Hive

    • MRS 3.1.2-LTS.6_004: Spark2x

    • MRS 3.1.2-LTS.6_006: Flink

    • MRS 3.1.2-LTS.6_008: Kafka

    • MRS 3.1.2-LTS.6_009: Flume

    • MRS 3.1.2-LTS.6_013: Loader

    • MRS 3.1.2-LTS.6_014: Hue

    • MRS 3.1.2-LTS.6_015: Ooize

    • MRS 3.1.2-LTS.6_018: DBService

    • MRS 3.1.2-LTS.6_019: ZooKeeper

    • MRS 3.1.2-LTS.6_022: Ranger

    • MRS 3.1.2-LTS.6_023: HetuEngine

    • MRS 3.1.2-LTS.6_024: Tez

    • MRS 3.1.2-LTS.6_025: ClickHouse

For example, the component_id of Hadoop is MRS 3.2.0-LTS.2_001.

componentName

String

Component name

componentVersion

String

Component version

componentDesc

String

Component description

Table 4 NodeGroup parameter description

Parameter

Type

Description

groupName

String

Node group name

nodeNum

Integer

Number of nodes. The value ranges from 0 to 500. The minimum number of Master and Core nodes is 1 and the total number of Core and Task nodes cannot exceed 500.

nodeSize

String

Instance specifications of a node

nodeSpecId

String

Instance specification ID of a node

nodeProductId

String

Instance product ID of a node

vmProductId

String

VM product ID of a node

vmSpecCode

String

VM specifications of a node

rootVolumeSize

Integer

System disk size of a node. This parameter is not configurable and its default value is 40 GB.

rootVolumeProductId

String

System disk product ID of a node

rootVolumeType

String

System disk type of a node

rootVolumeResourceSpecCode

String

System disk product specifications of a node

rootVolumeResourceType

String

System disk product type of a node

dataVolumeType

String

Data disk storage type of a node. Currently, SATA, SAS and SSD are supported.

  • SATA: Common I/O

  • SAS: High I/O

  • SSD: Ultra-high I/O

dataVolumeCount

Integer

Number of data disks of a node

dataVolumeSize

String

Data disk storage space of a node

dataVolumeProductId

String

Data disk product ID of a node

dataVolumeResourceSpecCode

String

Data disk product specifications of a node

dataVolumeResourceType

String

Data disk product type of a node

Table 5 bootstrap_scripts parameter description

Parameter

Type

Description

name

String

Name of a bootstrap action script. It must be unique in a cluster.

The value can contain only digits, letters, spaces, hyphens (-), and underscores (_) and cannot start with a space.

The value can contain 1 to 64 characters.

uri

String

Path of the shell script. Set this parameter to an OBS bucket path or a local VM path.

  • OBS bucket path: Enter a script path manually. For example, enter the path of the public sample script provided by MRS. Example: s3a://bootstrap/presto/presto-install.sh. If dualroles is installed, the parameter of the presto-install.sh script is dualroles. If worker is installed, the parameter of the presto-install.sh script is worker. Based on the Presto usage habit, you are advised to install dualroles on the active Master nodes and worker on the Core nodes.

  • Local VM path: Enter a script path. The script path must start with a slash (/) and end with .sh.

parameters

String

Bootstrap action script parameters

nodes

Array String

Type of a node where the bootstrap action script is executed. The value can be Master, Core, or Task.

active_master

Boolean

Whether the bootstrap action script runs only on active Master nodes.

The default value is false, indicating that the bootstrap action script can run on all Master nodes.

before_component_start

Boolean

Time when the bootstrap action script is executed. Currently, the following two options are available: Before component start and After component start

The default value is false, indicating that the bootstrap action script is executed after the component is started.

fail_action

String

Whether to continue executing subsequent scripts and creating a cluster after the bootstrap action script fails to be executed.

  • continue: Continue to execute subsequent scripts.

  • errorout: Stop the action.

The default value is errorout, indicating that the action is stopped.

Note

You are advised to set this parameter to continue in the commissioning phase so that the cluster can continue to be installed and started no matter whether the bootstrap action is successful.

start_time

String

Execution time of one boot operation script.

state

String

Running state of one bootstrap action script

  • PENDING

  • IN_PROGRESS

  • SUCCESS

  • FAILURE

Example

  • Example request

    None.

  • Example response

    None.

Status Code

Table 6 describes the status code of this API.

Table 6 Status code

Status Code

Description

200

Cluster details have been queried successfully.

For the description about error status codes, see Status Codes.