Changing Specifications
Function
This API is used to modify the specifications of a cluster. Only the specifications of ESS nodes can be modified.
Calling Method
For details, see Calling APIs.
URI
POST /v1.0/{project_id}/clusters/{cluster_id}/flavor
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details about how to obtain the project ID and name, see Obtaining a Project ID and Name. |
cluster_id |
Yes |
String |
ID of the cluster whose specifications you want to change. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
newFlavorId |
Yes |
String |
This parameter is obtained by calling the Obtaining the Instance Specifications List API. The API compares the values of the name attribute and obtains an appropriate flavor. The old and new node specifications must be under the same Elasticsearch engine version. |
needCheckReplica |
No |
Boolean |
Whether to verify replicas. The value can be true or false. Replica verification is enabled by default.
|
needCheckClusterStatus |
No |
Boolean |
Whether to check the cluster status. The value can be true or false. The default value is true.
|
Response Parameters
None
Example Requests
POST /v1.0/6204a5bd270343b5885144cf9c8c158d/clusters/4f3deec3-efa8-4598-bf91-560aad1377a3/flavor { "needCheckReplica" : false, "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2", "needCheckClusterStatus" : true }
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 does not meet one of the preconditions that the requester puts on the request. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot