Changing Specifications

This API is used to modify the specifications of a cluster. Only the nodes of the ESS type can be modified.

You can debug this API through automatic authentication in API Explorer or use the SDK sample code generated by API Explorer.

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

**Table 1** Path Parameters
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 cluster whose specifications you want to change.

**Table 2** Request body parameters
Parameter	Mandatory	Type	Description
needCheckReplica	No	Boolean	Whether to check replicas. The value can be true or false. The check is enabled by default. true: Replicas are checked. false: Replicas are not checked.
newFlavorId	Yes	String	ID of the new flavor. This parameter is obtained by calling the [Obtaining the Instance Specifications List] (ListFlavors.xml) API. The API compares the values of the name attribute and obtains the ID of the flavor higher than the current flavor. Only the node specifications of the same Elasticsearch engine version can be changed.
isAutoPay	No	Integer	Whether to enable automatic payment from your Huawei Cloud account. This parameter takes effect only for yearly/monthly clusters. 1: Yes. (Discounts and coupons are automatically selected. The fee will be automatically deducted from your Huawei Cloud account.) If the automatic payment fails, an unpaid order will be generated, and you need to manually complete the payment. (During manual payment, you can still modify the discounts and coupons that were automatically selected.) 0: No. (The customer needs to manually pay for the bill. Discounts and coupons can be used.) The default value is 0.

None

{
  "needCheckReplica" : false,
  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2",
  "isAutoPay" : 1
}

{
  "needCheckReplica" : false,
  "newFlavorId" : "35b060a4-f152-48ce-8773-36559ceb81f2"
}

None

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.