Forcibly Restarting VMs in a Cluster
Function
A cluster is unavailable during the restart. Exercise caution when performing this operation. During the restart of a running cluster, the Logstash process is automatically stopped. If Keepalive is disabled for pipes, all running pipes are stopped. If Keepalived is enabled, Logstash will try restoring these pipes. If Logstash is restarted within 10 minutes, the pipes will be restored to running. Otherwise the restoration will fail.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/reboot
Parameter | Mandatory | Type | Description |
|---|---|---|---|
project_id | Yes | String | Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name. |
cluster_id | Yes | String | ID of the target cluster |
Request Parameters
None
Response Parameters
None
Example Requests
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/reboot
Example Responses
None
Status Codes
Status Code | Description |
|---|---|
200 | Request succeeded. |
400 | Invalid request. Modify the request instead of retrying. |
409 | The request cannot be processed due to a conflict. This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict. |
412 | The server does not meet one of the requirements that the requester puts on the request. |
Error Codes
See Error Codes.
- URI