All Products
Search
Document Center

E-MapReduce:IncreaseNodes

更新時間:Oct 17, 2024

Scale out the node group.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringYes

The ID of the region in which you want to create the instance.

cn-hangzhou
ClusterIdstringYes

The ID of the cluster.

c-b933c5aac8fe****
NodeGroupIdstringYes

The ID of the node group. The target node group to which you want to scale out the cluster.

ng-869471354ecd****
IncreaseNodeCountintegerYes

The number of nodes. The number of incremental nodes for this scale-out. Valid values: 1 to 500.

3
AutoPayOrderbooleanNo

Indicates whether to automatically pay for the orders involved in the scale-out operation. This parameter takes effect only when the PaymentType parameter is set to Subscription. Valid values:

  • true: automatically pays for the order involved in this operation.
  • false: does not automatically pay for the orders involved in this operation.

Default value: false

false
AutoRenewbooleanNo

Specifies whether to enable auto-renewal for nodes. Valid values:

  • true
  • false (default value)
false
PaymentDurationintegerNo

The subscription duration. Valid values when the PaymentDurationUnit value is Month: 1, 2, 3, 4, 5, 6, 7, 8, 9, 12, 24, 36, 48, and 60.

12
PaymentDurationUnitstringNo

The unit of the subscription duration. Valid values:

  • Month
Month
ApplicationConfigsarrayNo

The application configurations. You can specify a maximum of 1,000 items.

ApplicationConfigApplicationConfigNo

The application configuration.

MinIncreaseNodeCountintegerNo

The minimum number of nodes that can be added. Valid values: 1 to 500.

  • If you configure this parameter, and the number of available Elastic Compute Service (ECS) instances is less than the value of the IncreaseNodeCount parameter, the system tries to add nodes based on the number specified by the MinIncreaseNodeCount parameter. If the minimum number of nodes are added, the scale-out status is PARTIAL_COMPLETED.
  • If you do not configure this parameter, and the number of available ECS instances is less than the value of the IncreaseNodeCount parameter, the scale-out process fails. The scale-out status is FAILED.

Response parameters

ParameterTypeDescriptionExample
object

The returned data.

OperationIdstring

The ID of the operation.

op-13c37a77c505****
RequestIdstring

The ID of the request.

DD6B1B2A-5837-5237-ABE4-FF0C8944****

Examples

Sample success responses

JSONformat

{
  "OperationId": "op-13c37a77c505****",
  "RequestId": "DD6B1B2A-5837-5237-ABE4-FF0C8944****"
}

Error codes

HTTP status codeError codeError message
400OperationDeniedThe operation is invalid. %s
400OutOfStockThe requested resource is sold out in the specified zone, try other types of resources or other regions and zones.
400QuotaExceededRequest fail due to quota exceed. %s
400AccountExceptionAccount exception. %s
400ConcurrentModificationThe request on %s failed due to multiple requests to change this object were submitted simultaneously. Wait a few minutes and try again.
400ConflictParametersParameters that must not be used together. %s
400IncompleteSignatureThe request signature is invalid.
400InvalidActionThe action %s requested is invalid.
400InvalidParameterThe specified parameter %s is not valid.
400InvalidParameterValueThe input parameter %s is invalid or out of range.
400MissingActionThe action %s requested is missing.
400MissingParameterThe input parameter %s that is mandatory for processing this request is not supplied.
400NotAuthorizedYou do not have permission to perform this action. %s
400ThrottlingExceptionThe request was denied due to request throttling. %s
404ResourceNotFoundThe resource not found by %s.
500InternalErrorThe request processing has failed due to some unknown error, exception or failure.
503ServiceFailureThe request has failed due to a temporary failure of %s service.
503ServiceUnavailableThe request has failed due to a temporary failure of the server.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-06-18The Error code has changed. The request parameters of the API has changedView Change Details
2024-02-23The Error code has changed. The request parameters of the API has changedView Change Details
2021-10-12The Error code has changedView Change Details