Modifies the number of nodes in a warehouse of an E-MapReduce (EMR) Serverless StarRocks instance.
Operation description
Before you call this operation, make sure that you understand the billing methods and pricing of EMR Serverless StarRocks instances.
Before you call this operation, take note of the following items:
- You can modify the number of nodes in a warehouse of only StarRocks instances of Standard Edition.
- The instance must be in the Running state.
- The number of frontend nodes (FEs) cannot be an even number, and you cannot reduce the number of FE nodes.
After you modify the number of nodes in a warehouse, the billing of nodes has the following changes:
- Pay-as-you-go StarRocks instances: You are charged based on the number of nodes.
- Subscription StarRocks instances: You are charged additionally based on the price difference between the number of nodes before and after the change and the remaining days of the billing cycle. The billing cycle starts from 00:00 the next day until the end of the subscription period.
Debugging
Authorization information
The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:
- Operation: the value that you can use in the Action element to specify the operation on a resource.
- Access level: the access level of each operation. The levels are read, write, and list.
- Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
- For mandatory resource types, indicate with a prefix of * .
- If the permissions cannot be granted at the resource level,
All Resourcesis used in the Resource type column of the operation.
- Condition Key: the condition key that is defined by the cloud service.
- Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
| Operation | Access level | Resource type | Condition key | Associated operation |
|---|---|---|---|---|
| sr:ModifyNodeNumber | get | *Instance acs:sr:{#regionId}:{#accountId}:instance/{#InstanceId} |
| none |
Request syntax
POST /webapi/resourceChange/modifyNodeNumber HTTP/1.1
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| InstanceId | string | Yes | The instance ID. | c-b25e21e24388**** |
| NodeGroupId | string | Yes | The warehouse ID. | ng-3d5ce6454354**** |
| Target | integer | Yes | The number of nodes to which you want to change to. | 3 |
Response parameters
Examples
Sample success responses
JSONformat
{
"HttpStatusCode": 200,
"RequestId": "32A44F0D-BFF6-5664-999A-218BBDE7****",
"Success": false,
"ErrCode": "InvalidParams",
"ErrMessage": "Invalid params: [instance not exists].",
"Data": 0,
"AccessDeniedDetail": "{ \"PolicyType\": \"AccountLevelIdentityBasedPolicy\", \"AuthPrincipalOwnerId\": \"xxx\", \"EncodedDiagnosticMessage\": \"xxx\", \"AuthPrincipalType\": \"xxx\", \"AuthPrincipalDisplayName\": \"xxx\", \"NoPermissionType\": \"ImplicitDeny\", \"AuthAction\": \"sr:xxx\" }"
}Error codes
For a list of error codes, visit the Service error codes.