Error Codes

Updated on 2022-12-14 GMT+08:00

View PDF

Status Code	Error Code	Error Message	Measure
400	0171	Failed to collect job log details.	-
400	12000002	The parameter is invalid.	-
400	12000003	The cluster does not exist.	-
400	12000009	The parameter is invalid.	-
400	12000012	Tasks are being executed in the cluster. Subcontract period cluster is not allowed for clusters that are in this state. Scale-out or scale-in is not allowed for clusters that are not in the running state.	-
400	12000013	Failed to scale in the cluster (ID: xxx). The type and the quantity of nodes to be deleted are xxx and xxx, respectively. The task node does not exist.	-
400	12000014	Failed to scale out the cluster (ID: xxx). The type and the quantity of nodes to be added are xxx and xxx, respectively.	-
400	12000018	Scale-out or scale-in cannot be performed again because it is in progress.	-
400	12000019	Failed to obtain hosts of the cluster.	-
400	12000021	Clusters in the xxx state cannot be terminated.	-
400	120000212	Failed to obtain the AZs that you have permission to access.	-
400	12000023	Failed to obtain cluster details.	-
400	12000027	Failed to verify the subnet when creating the cluster xxx.	-
400	12000028	The cluster has a maximum of xxx Core and Task nodes.	-
400	12000029	Failed to obtain the quota.	-
400	12000030	The requested number of nodes in the cluster exceeds the available quota.	-
400	12000031	The requested number of vCPUs in the cluster exceeds the available quota.	-
400	12000032	The requested memory of the cluster exceeds the available quota.	-
400	12000033	The requested number of disks in the cluster exceeds the available quota.	-
400	12000034	The requested disk capacity of the cluster exceeds the available quota.	-
400	12000036	Failed to obtain product information.	-
400	12000038	Failed to obtain the security group.	-
400	12000041	Failed to obtain the cluster list.	-
400	12000042	Failed to create a cluster.	-
400	12000043	Duplicate cluster name: xxx.	-
400	12000044	The minimum memory of a Master node is xxx GB.	-
400	12000045	Insufficient quota of the security group.	-
400	12000046	Insufficient quota of the security group rule.	-
400	12000048	Product specification xxx does not exist.	-
400	12000050	Incorrect certificate.	-
400	12000052	No access rights.	-
400	12000053	Invalid billing type.	-
400	12000054	The operation is not supported.	-
400	12000059	Key pair xxx does not exist.	-
400	12000061	Failed to submit the job (cluster ID: xxx; job name: xxx; job ID: xxx).	-
400	12000062	Jobs cannot be submitted to a cluster in the xxx state.	-
400	12000063	Spark jobs cannot be submitted.	-
400	12000064	Jobs cannot be submitted or inquired to a security cluster by API.	-
400	12000080	The status of some nodes is not running in the cluster. Try again later.	-
400	12000081	The jar_path parameter cannot be left blank if the job type is MapReduce or Spark.	-
400	12000082	Node groups cannot be deleted in the cluster that is being scaled in or scaled out.	-
400	12000085	This interface does not support the cluster of this version.Please use the /v2/{project_id}/clusters/{cluster_id}/job-executions job submit interface.	-
400	12000086	This cluster version not support s3[an]: schema. Please use the obs: schema.	-
400	12000087	Failed to get billing records.	-
400	12000090	Products of the xxx specifications are no longer available in selected AZ.	-
400	12000092	Failed to get metadata of version xxx.	-
400	12000093	Metadata of version xxx not found.	-
400	12000094	The xxx in xxx version does not support the xxx flavor.	-
400	12000095	Patch xxx is unavailable.	-
400	12000099	Topology template of version xxx not found.	-
400	12000100	Failed to stop the cluster. Only running or abnormal clusters can be stopped.	-
400	12000101	Failed to start the cluster. Only stopped clusters can be started.	-
400	12000104	VPC\|ECS\|DSS\|DCC\|OpenStack service error.	-
400	12000105	VPC xxx does not exist.	-
400	12000106	Key pair xxx does not exist.	-
400	12000107	Invalid project ID: xxx.	-
400	12000108	Failed to verify the EIP when creating the cluster xxx.	-
400	12000109	Failed to bind the EIP to cluster xxx.	-
400	12000110	Failed to unbind the EIP from cluster xxx.	-
400	12000111	Failed to bind the EIP. The EIP xxx has been bound to another resource.	-
400	12000112	The EIP xxx does not exist.	-
400	12000113	Failed to update the EIP.	-
400	12000114	The hive_script_path parameter cannot be left blank if the job type is Hive or SparkScript.	-
400	12000115	The ECS group quota is insufficient.	-
400	12000116	The VPC quota is insufficient. Select the existing VPC or increase the quota.	-
400	12000117	The subnet quota is insufficient. Select the existing subnet or increase the quota.	-
400	12000118	Failed to create the security group rule.	-
400	12000119	The security group rule already exists.	-
400	12000121	Failed to submit a request to scale out the Yearly/Monthly cluster. Scale-out is not allowed because the cluster has an unpaid order. Scale out the cluster again after you pay the order.	-
400	12000122	EPS service error.	-
400	12000123	Failed to update Task node information because the number of Task nodes is not 0.	-
400	12000124	In the cluster xxx, the number of Task nodes can be adjusted only using auto scaling.	-
400	12000125	Failed to update Task node information, because the cluster state is scaling out or scaling in.	-
400	12000126	Failed to obtain authentication information.	-
400	12000127	Failed to lock cluster operation.	-
400	12000128	Failed to unlock cluster operation.	-
400	12000129	Master node specifications cannot be scaled up for a cluster that is not in the running state.	-
400	12000130	Specifications available for scale-up not found.	-
400	12000131	Master node specifications cannot be scaled up for a non-HA cluster.	-
400	12000132	vCPUs and memory cannot be reduced in the specification scale-up.	-
400	12000133	Specification scale-up is not available for this type of nodes.	-
400	12000134	Failed to scale up the Master node specifications.	-
400	12000135	Master nodes available for specification scale-up not found	-
400	12000138	Failed to get max server Group members.	-
400	12000139	All evs volume type is sellout, please try again later.	-
400	12000140	Evs volume type:xxx is sellout, please try again later.	-
400	12000141	The disk size of a node cannot be less than {value} GB.	-
400	12000142	The disk size cannot exceed 32,000 GB.	-
400	12000209	Either a VPC ID or name is required.	-
400	12000210	Either a subnet ID or name is required.	-
400	12000233	Insufficient resources for flavor xxx. Reduce the purchase quantity and try again. Alternatively, select another instance type or flavor, or switch the AZ or region to select your desired product.	-
400	12000234	Insufficient resources for the flavor xxx of the node to be scaled out. Reduce the purchase quantity and try again.	-
400	12000360	Cluster name cannot be updated for a cluster that is in the terminating or terminated state.	-
400	12000361	Only offline cluster is allowed to modify manager access ip.	-
400	12000362	Cluster id is already exist or not universally unique identifier format.	-
400	12000363	The offline cluster with same management node IPs[xxx] already exists.	-
400	12005001	The number of tags in one cluster must not exceed xxx.	-
400	12005002	Tag xxx does not comply with the specifications. The tag key and value cannot start or end with a space and cannot contain any of the following characters: =*<>\\,\|/.	-
400	13000046	Security group xxx does not exist.	-
400	MRS.1010	The RDS instance whose ID is xxx is not found. The status (xxx) of RDS instance xxx is abnormal.	-
401	12000001	Invalid authentication	-
401	12000136	Permission denied. Error message: Policy doesn't allow bss:order:update to be performed.	-
404	12000057	Failed to obtain the file list.	-
404	12005003	The tag key xxx does not exist in cluster xxx.	-
500	0023	Failed to obtain cluster details.	-
500	0056	Jobs cannot be submitted to a cluster in the xxx state.	-
500	0057	Spark jobs cannot be submitted.	-
500	0093	Metadata of version xxx not found.	-
500	0160	Failed to kill the job.	-
500	0161	Failed to delete jobs in batches.	-
500	0162	Failed to query the job.	-
500	0165	Failed to verify the SQL statement.	-
500	0166	Failed to query a job list.	-
500	0167	The v2 job API cannot be accessed.	-
500	0168	Hive jobs cannot be submitted.	-
500	0169	Flink jobs cannot be submitted.	-
500	0170	Failed to collect job log directory information.	-
500	0172	Failed to collect the SQL job result.	-
500	0173	Failed to submit the job (cluster ID: xxx; job name: xxx).	-
500	0174	Failed to query the job.	-
500	0175	Failed to kill the job.	-
500	0176	The job does not exist.	-
500	0177	The number of jobs running in each cluster cannot exceed 10.	-
500	0178	The job ID cannot be left blank.	-
500	0179	The job type must be SparkSql or SparkScript.	-
500	0180	The job is being submitted.	-
500	0181	The SQL job result collection is empty.	-
500	0182	Failed to read the SQL job result.	-
500	0183	The job is running.	-
500	0185	The log type does not exist.	-
500	0187	The log aggregation path is empty. Logs cannot be queried.	-
500	0188	The job query result is empty. Logs cannot be obtained.	-
500	0189	Failed to delete the job list.	-
500	0190	The user who submits the job cannot be empty.	-
500	0191	Failed to query the user who submits the job on MRS Manager.	-
500	0192	The current user does not exist on MRS Manager. Grant the user sufficient permissions on IAM and then perform IAM user synchronization on the Dashboard tab page.	-
500	0193	Failed to operate the database job records.	-
500	0194	Failed to start the launcher and submit the job.	-
500	0199	Failed to delete the jobs.	-
500	0200	Failed to kill the jobs on Yarn.	-
500	0201	The job does not exist.	-
500	0202	Too many jobs are being submitted, please try again later.	-
500	0211	The maximum number of bound security groups has been reached. A maximum of four security groups can be bound, excluding the default security group that is automatically created.	-
500	12000004	Internal server error.	-
500	12000020	Failed to terminate the cluster.	-
500	120000213	The region [xxx] does not exist.	-
500	120000214	No permission to access the AZs [xxx]. The following AZs [xxx] can be accessed.	-
500	12000055	Failed to open the file.	-
500	12000060	The number of running jobs per cluster cannot exceed xxx.	-
500	12000068	If the job type is Hive or Spark Script, the value of the mains should not be left blank.	-
500	12000069	If the job type is MapReduce or Spark, the value of the libs should not be left blank.	-
500	12000070	An error occurred while accessing Knox.	-
500	12000071	The Executor server has an internal error.	-
500	12000073	Failed to access the HDFS directory.	-
500	12000102	Failed to stop the cluster.	-
500	12000103	Failed to start the cluster.	-
500	12000154	IAM synchronization is in progress and cannot be triggered again in the same cluster. Cluster ID: xxx	-
500	12000156	Failed to query Iam group	-
500	12000157	Failed to query Iam user or role	-
500	12000163	Failed to query Manager user.	-
500	12000164	Failed to query Manager user group.	-
500	130000002	The token is invalid.	-
500	MRS.0010	Dataconnector error.	-
500	MRS.0011	SQL typed xxx can not run on the cluster which not installed dependent components. Cannot execute SQL on a cluster in the xxx state. Not support sql execution in cluster version xxx. Request with multiple SQL is not support. Failed to submit the SQL request to Executor (cluster ID: xxx).	-
500	MRS.0205	Failed to sync agency mapping configuration to cluster.	-
500	MRS.0206	Updating agency mapping task is running.	-
500	MRS.0207	Parse Json format failed.	-
500	MRS.0208	Create or modify policy failed.	-
500	MRS.0209	Assign policy to agency failed.	-
500	MRS.0210	No secu_admin policy.	-
500	MRS.0211	Failed to obtain new agency or new agency does not exist.	-
500	MRS.0212	Updating ECS agency task is running.	-
500	MRS.0216	Failed to update ECS metadata.	-
500	MRS.0217	Failed to unbind policy.	-
500	MRS.0218	Failed to check whether policies are exist or not.	-