Help Center/ Cloud Search Service/ API Reference/ API V1/ Logstash/ Forcibly Restarting VMs in a Cluster

Updated on 2025-08-15 GMT+08:00

View PDF

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.

Calling Method

For details, see Calling APIs.

URI

POST /v1.0/{project_id}/clusters/{cluster_id}/reboot

**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 target cluster. 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

None

Response Parameters

Status code: 200

Request succeeded.

None

Example Requests

Forcibly restart VMs in a cluster.

POST https://{Endpoint}/v1.0/{project_id}/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.