Restarting a Cluster (V2)

Function

This API is used to restart nodes of all or some types in the current cluster.

If a cluster is available, ensure that it has stopped handling service requests, such as importing and searching for data. Otherwise, the cluster restart may cause data loss.

Calling Method

For details, see Calling APIs.

URI

POST /v2.0/{project_id}/clusters/{cluster_id}/restart

**Table 1** Path Parameters
Parameter	Mandatory	Type	Description
project_id	Yes	String	Definition: Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. Constraints: N/A Value range: Project ID of the account. Default value: N/A
cluster_id	Yes	String	Definition: ID of the cluster you want to restart. For details about how to obtain the cluster ID, see Obtaining the Cluster ID. Constraints: N/A Value range: Cluster ID. Default value: N/A

Request Parameters

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
type	Yes	String	Definition: Restart mode. Value range: node: restarts nodes. role: restarts roles.
value	Yes	String	Operation parameters. Parameter description: When the operation role is node, the value is the node ID. You can obtain the ID attribute in instances by referring to Querying Cluster Details. When the operation role is role, the value is one or multiple node types (such as ess, ess-master, ess-client, and ess-cold).

Response Parameters

Status code: 200

Request succeeded.

None

Example Requests

Restart nodes of all or some types in the current cluster.

POST https://{Endpoint}/v2.0/{project_id}/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/restart

{
  "type" : "role",
  "value" : "ess"
}

Example Responses

None

Status Codes

Status Code	Description
200	Request succeeded.
400	Invalid request. Modify the request before retry.
409	The request could not be completed due to a conflict with the current state of the resource. The resource that the client attempts to create already exists, or the update request fails to be processed because of a conflict.
412	The server did not meet one of the preconditions contained in the request.