IncreaseNodes - E-MapReduce - Alibaba Cloud Documentation Center

Scales out a target node group.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

emr:IncreaseNodes

update

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID.	cn-hangzhou
ClusterId	string	Yes	The cluster ID.	c-b933c5aac8fe****
NodeGroupId	string	Yes	The ID of the node group to scale out.	ng-869471354ecd****
IncreaseNodeCount	integer	Yes	The number of nodes to add. Valid values: 1 to 500.	3
AutoPayOrder	boolean	No	Specifies whether to automatically pay for the order. This parameter is effective only when the PaymentType of the node group is Subscription. Valid values: true: Automatically pays for the order. false: Does not automatically pay for the order. Default value: false.	false
AutoRenew	boolean	No	Specifies whether to enable auto-renewal for the added nodes. The default value is false. Valid values: true: Enables auto-renewal. false: Disables auto-renewal.	false
PaymentDuration	integer	No	The subscription duration. If PaymentDurationUnit is set to Month, valid values are 1, 2, 3, 4, 5, 6, 7, 8, 9, 12, 24, 36, 48, and 60.	12
PaymentDurationUnit	string	No	The unit of the subscription duration. Valid values: Month: The unit is month.	Month
ApplicationConfigs	array	No	The application configurations. The number of array elements can range from 1 to 1,000.	Month
	ApplicationConfig	No	The application configuration.
MinIncreaseNodeCount	integer	No	The minimum number of nodes to add in this scale-out operation. The value must be between 1 and 500. If you set this parameter and the available ECS inventory is less than IncreaseNodeCount, the system attempts to create at least the number of nodes specified by MinIncreaseNodeCount. The scale-out flow is then marked as `PARTIAL_COMPLETED`. If you do not set this parameter and the available ECS inventory is less than IncreaseNodeCount, the scale-out flow fails and is marked as `FAILED`.
Promotions	array	No
	Promotion	No

Response elements

Element	Type	Description	Example
	object	The returned data.
OperationId	string	The operation ID.	op-13c37a77c505****
RequestId	string	The request ID.	DD6B1B2A-5837-5237-ABE4-FF0C8944****

Examples

Success response

JSON format

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

Error codes

HTTP status code	Error code	Error message
400	OperationDenied	The operation is invalid. %s
400	OutOfStock	The requested resource is sold out in the specified zone, try other types of resources or other regions and zones.
400	QuotaExceeded	Request fail due to quota exceed. %s
400	AccountException	Account exception. %s
400	ConcurrentModification	The request on %s failed due to multiple requests to change this object were submitted simultaneously. Wait a few minutes and try again.
400	ConflictParameters	Parameters that must not be used together. %s
400	IncompleteSignature	The request signature is invalid.
400	InvalidAction	The action %s requested is invalid.
400	InvalidParameter	The specified parameter %s is not valid.
400	InvalidParameterValue	The input parameter %s is invalid or out of range.
400	MissingAction	The action %s requested is missing.
400	MissingParameter	The input parameter %s that is mandatory for processing this request is not supplied.
400	NotAuthorized	You do not have permission to perform this action. %s
400	ThrottlingException	The request was denied due to request throttling. %s
500	InternalError	The request processing has failed due to some unknown error, exception or failure.
404	ResourceNotFound	The resource not found by %s.
503	ServiceFailure	The request has failed due to a temporary failure of %s service.
503	ServiceUnavailable	The request has failed due to a temporary failure of the server.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.