Resets and restores a cluster.
Operation description
You can call the operation to reset and restore a cluster only when the cluster is in the Exception state. You can call the ListClusters operation to query the ID and status of a cluster. We recommend that you export all job data before you restore a cluster. When you reset and restore a cluster, take note of the following impacts:
- The system disks of all nodes are changed. By default, new system disks are configured based on the settings that you specified when the cluster was created.
- The data on the system disks and data disks of all cluster nodes is lost. The data includes user information, job information, scheduler queue information, and configuration data of auto-scaling queues. However, the data on Apsara File Storage NAS file systems is retained.
- The self-managed queues in the cluster are deleted. All nodes are retained and migrated to the default queue of the cluster.
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:
- The required resource types are displayed in bold characters.
- 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 |
|---|---|---|---|---|
| ehpc:RecoverCluster | WRITE |
|
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| ClusterId | string | Yes | The cluster ID. The cluster must be in the Exception state. You can call the ListClusters operation to query the ID and status of a cluster. | ehpc-hz-FYUr32**** |
| OsTag | string | No | The tag of the system image. You can call the ListImages and ListCustomImages operations to query the image tags supported by Elastic High Performance Computing (E-HPC). | CentOS_7.2_64 |
| AccountType | string | No | The service type of the domain account. Valid values:
Default value: nis. | nis |
| SchedulerType | string | No | The type of the scheduler. Valid values:
Default value: pbs. | pbs |
| ImageOwnerAlias | string | No | The type of the image. Valid values:
Default value: system. | system |
| ImageId | string | No | The image ID. You can call the ListImages and ListCustomImages operations to query the images that are supported by E-HPC. | m-bp18133n0335yq**** |
| ClientVersion | string | No | The version of the E-HPC client. The default value is the latest version of the client. You can call the ListCurrentClientVersion operation to query the latest version of the E-HPC client. | 1.0.76 |
Response parameters
Examples
Sample success responses
JSONformat
{
"TaskId": "18FB21E3-F423-4B84-BB63-D8887A29****",
"RequestId": "18FB21E3-F423-4B84-BB63-D8887A29****"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | InvalidParams | The specified parameter %s is invalid. | The specified parameter %s is invalid. |
| 400 | InDebt | Your account has overdue payments. | Your account has overdue payments. |
| 400 | OrderError.InsufficientBalance | The account balance is insufficient. Please add funds first and try again. | Your account has overdue payments. Add funds to your account and try again. |
| 400 | OrderError.InstHasUnpaidOrder | Your account has an unpaid order. | Your account has an unpaid order. Please pay the order and try again. |
| 400 | OrderError.Arrearage | Your account balance is less than CNY 100. Please add funds to your account and try again. | Your account balance is less than CNY 100. Add funds to your account and try again. |
| 400 | OrderError.NoCard | No credit card is bound to your account. | You have not bound a card. Please perform binding first. |
| 400 | OrderError.InvalidPayMethod | No valid default payment method is specified for your account. | No valid payment method is found. Please check again. |
| 400 | OrderError.NoRealNameAuthentication | You have not completed the real name authentication. | You must complete the real-name verification first. |
| 400 | OrderError.NoRealNameRegistration | Real name registration is required for instances launched in mainland China. | To purchase cloud services in mainland China regions on the international site, the user must first complete real-name registration. |
| 400 | OrderError.UserProfileIncomplete | You have not completed your user profile. | The user has not completed personal information on the international site. |
| 400 | InvalidVpc | The specified VPC is invalid. | The VPC information is invalid. |
| 400 | InvalidVolume | The specified volume is invalid. | The specified volume is invalid. |
| 400 | InvalidSoftware | The specified software is not supported. | The requested software is not supported. |
| 400 | InvalidVolumeProtocal | The specified volume protocol is invalid. | The storage protocol is invalid. |
| 400 | InvalidVolumeMountpoint | The specified volume mount point is invalid. | The specified volume mount point is invalid. |
| 403 | TooManyClusters | The number of user clusters exceeds the quota. | The number of user clusters exceeds the quota. By default, the number of user clusters cannot exceed three. |
| 403 | TooManyComputes | The number of computing nodes exceeds the quota. | The number of computing nodes exceeds the quota. |
| 403 | TooManyLogins | The maximum number of logged on nodes is exceeded. | The maximum number of logged on nodes is exceeded. The default maximum value is 2. |
| 403 | TooManyScc | The maximum number of SCC instances is exceeded. | The maximum number of SCC instances is exceeded. The default maximum value is 15. |
| 403 | QuotaExceeded.PrivateIpAddress | Insufficient private IP addresses in vSwitch: %s. | Insufficient private IP addresses in vSwitch: %s. |
| 403 | ConflictOpt | A conflicting operation is running. | A conflicting operation is running. Please try again later. |
| 403 | ImageNotSupported | The specified image is not supported. | The specified image does not exist. Change the image and try again. |
| 404 | ImageNotFound | The specified image does not exist. | The specified image does not exist. Please verify the parameter. |
| 404 | VolumeNotFound | The specified volume does not exist. | The specified storage does not exist. Please verify the parameter. |
| 404 | VpcNotFound | The specified VPC does not exist. | The specified VPC does not exist. |
| 404 | ClusterNotFound | The specified cluster does not exist. | The specified instance does not exist. |
| 406 | EcsError | An error occurred while calling the ECS API operation. | An error occurred while calling the ECS API operation. |
| 406 | NasError | NAS API request failed. | Failed to request the NAS interface. |
| 406 | EipError | The EIP API request failed. | EIP API request failed. |
| 406 | OrderError | An order request error occurred. | An order request error occurred. |
| 406 | FailToGenId | Generating cluster ID failed. | Failed to generate the cluster ID. Please try again. |
| 406 | DbError | A database service error occurred. | Database request failed. |
| 406 | AliyunError | An Alibaba Cloud product error occurred. | An Alibaba Cloud product error occurred. |
| 407 | NotAuthorized | You are not authorized by RAM for this request. | The request is not authorized by RAM. |
| 500 | UnknownError | An unknown error occurred. | An unknown error occurred. |
| 503 | ServiceUnavailable | The request has failed due to a temporary failure of the server | The request has failed due to a temporary failure of the server. |
For a list of error codes, visit the Service error codes.