DIS Server-Side Error Codes

441

DIS.4100

Authorization error.

The signature information generated using AK and SK is incorrect.

Ensure that the signature information in the request header is correct.

441

DIS.4101

Authorization header cannot be empty.

The signature information generated using AK and SK is blank.

Ensure that the signature information is generated.

441

DIS.4102

Incorrectly parsed authorization header.

The signature cannot be parsed.

Ensure that the signature information in the request header is correct.

441

DIS.4103

Empty X-Sdk-Date header.

The X-Sdk-Date field in the request header is blank.

Ensure that the X-Sdk-Date field in the request header is not blank.

441

DIS.4104

Error parsing X-Sdk-Date header.

The X-Sdk-Date field in the request header cannot be parsed.

Ensure that the X-Sdk-Date field in the request header is correct.

441

DIS.4105

Invalid X-Sdk-Date header.

The X-Sdk-Date field in the request header is invalid.

Ensure that the X-Sdk-Date field in the request header is correct.

441

DIS.4106

Empty AcessKey header.

The Authorization field of the request header does not contain AK.

Ensure that AK is contained in the Authorization field.

441

DIS.4107

Invalid AcessKey header.

AK in the Authorization field of the request header is invalid.

Ensure that AK is valid and correct.

441

DIS.4108

Empty ServiceName header.

The Authorization field of the request header does not contain the service name.

Ensure that the Authorization field of the request header contain service name dis.

441

DIS.4109

The Authorization header must contain the following field: {Credential,SignedHeaders,Signature;}

The Authorization field of the request header is incorrect.

Ensure that the Authorization field of the request header contains Credential, SignedHeaders, and Signature.

441

DIS.4110

Empty Signature header.

The Authorization field of the request header does not contain SignedHeaders.

Ensure that the signature generation mode is correct.

441

DIS.4111

Invalid Region header.

The region in the Authorization field of the request header is invalid.

Ensure that the region is valid.

441

DIS.4112

Invalid authorization request.

The signature information generated using AK and SK is incorrect.

Ensure that the signature generation mode and the information about AK, SK, and region are correct.

441

DIS.4113

Empty Token header.

When token authentication is used, the X-Auth-Token field of the request header is blank.

Ensure that the X-Auth-Token field of the request header is not blank.

441

DIS.4114

Invalid Token header.

When token authentication is used, the X-Auth-Token field of the request header is invalid.

Ensure that the X-Auth-Token field of the request header is valid.

403

DIS.4116

Invalid RBAC.

User operations are restricted.

Ensure that all bills have been paid and DIS operating permissions have been obtained.

400

DIS.4117

Invalid Project Id.

Invalid project ID.

Ensure that the project ID is valid and correct.

400

DIS.4200

Invalid request.

The user request is invalid.

Ensure that the request is invalid by referring to API Reference.

400

DIS.4201

Invalid partition_id.

Invalid partition ID.

Ensure that the partition ID is valid.

400

DIS.4202

Empty request.

The user request is empty.

Enter a valid request.

400

DIS.4203

Invalid monitoring period.

The start time for querying monitoring information is invalid.

Enter a valid timestamp.

400

DIS.4204

The monitoring period cannot be longer than 7 days.

Only the monitoring information generated in the recent seven days can be queried.

Query the monitoring information generated in the recent seven days.

400

DIS.4208

Invalid MRS cluster.

The MRS cluster entered during MRS dump task creation is invalid.

Ensure the MRS cluster name and ID are correct and the cluster is running in security mode.

400

DIS.4209

Invalid metrics label.

The monitoring metric entered during monitoring information query is invalid.

Check and correct the monitoring metric by referring to API Reference.

400

DIS.4215

Invalid cursor type.

The cursor type entered during the data cursor acquisition is invalid.

Check and correct the cursor type by referring to API Reference.

400

DIS.4216

Invalid sequence_number.

The starting sequence number entered during data cursor acquisition is invalid.

Enter a valid starting sequence number.

400

DIS.4217

Invalid partition cursor.

The partition cursor entered during data download from DIS is invalid.

Obtain the partition cursor again and download the data.

400

DIS.4219

The file is constantly resent.

The file has been received.

Do not upload the file again.

400

DIS.4220

The block whose sequence number is %s needs to be resent.

The file block needs to be uploaded again.

Upload the corresponding file block as instructed.

400

DIS.4221

Block seq %s is expected

Duplicate file blocks are uploaded.

Upload the file block from the one expected by the system.

400

DIS.4222

Block seq %s is expected.

The uploaded file blocks are not consecutive.

Upload the file block from the one expected by the system.

400

DIS.4223

The file size exceeds the limit.

The file capacity exceeds the upper limit.

Split the file and upload it again.

400

DIS.4224

The sequence number is out of range.

The starting sequence number entered during data cursor acquisition is invalid.

Enter a valid starting sequence number.

400

DIS.4225

Expired partition cursor.

The partition cursor entered during data download from DIS expires.

Obtain the partition cursor again and download the data.

400

DIS.4226

A partition iterator error occurred or a record to which the SN corresponds has expired. Try to obtain the partition iterator again.

The starting sequence number of the partition cursor entered during data acquisition expires.

Obtain the data cursor and use the new cursor to obtain data.

400

DIS.4300

Request error.

The request body is incorrect.

Correct the request body by referring to API Reference.

400

DIS.4301

The stream does not exist.

The stream does not exist.

Ensure that the stream exists.

400

DIS.4302

The partition does not exist.

The stream partition does not exist.

Ensure that the partition ID exists.

400

DIS.4303

Exceeded traffic control limit.

The flow control limit is exceeded.

Add partitions or reduce the upload rate.

400

DIS.4305

Too many stream requests.

An excessive number of user requests are generated at the same time.

Decrease the requesting frequency and try again.

400

DIS.4306

The bucket does not exist.

The OBS bucket does not exist.

Ensure that the OBS bucket exists.

400

DIS.4307

The stream already exists.

The stream already exists.

Enter a new stream name.

400

DIS.4308

Insufficient quota.

Insufficient stream or partition quotas.

Release the resources that will not be used to ensure that the quota limit is not exceeded or submit a service ticket to increase the quota limit.

400

DIS.4309

Too many request failures. Please try again later.

The IP address is added to the blacklist.

Ensure that the authentication information and request are valid and try again later.

400

DIS.4310

OBS access error.

OBS failed to be accessed.

Ensure that the user has the permission to access OBS.

400

DIS.4329

app quota exceeded.

The application quota exceeds the limit.

Release the applications that are not used.

400

DIS.4330

app already exist.

An application with the same name already exists.

Enter a new application name.

400

DIS.4331

app is using.

The application fails to be deleted.

Ensure that the application that you want to delete is not being used.

400

DIS.4332

app not found.

The specified application does not exist.

Ensure the application name is correct.

400

DIS.4335

Invalid IAM agency.

The IAM agency used during dump task creation is invalid.

Ensure that dis_admin_agency created by DIS or the user-defined IAM agency exists and permission is complete.

400

DIS.4336

Invalid HDFS path.

The MRS HDFS path entered during MRS dump task creation is invalid.

Ensure that the MRS HDFS path exists.

400

DIS.4337

The DLI database does not exist.

The DLI database entered during DLI dump task creation does not exist.

Ensure that the DLI database exists.

400

DIS.4338

The DLI table does not exist.

The DLI table entered during DLI dump task creation does not exist.

Ensure that the DLI table exists and is an internal table.

400

DIS.4350

Invalid DWS cluster.

The DWS cluster entered during DWS dump task creation does not exist.

Ensure that the DWS cluster exists and is running properly.

400

DIS.4351

Invalid KMS userKey.

The KMS key entered during DWS dump task creation is invalid.

Ensure that the KMS key exists.

400

DIS.4354

The transfer task does not exist.

The dump task to be deleted or updated does not exist.

Ensure that the dump task exists.

400

DIS.4355

The transfer task already exists.

When you create a dump task in a stream, another dump task with the same name already exists in this stream.

Enter a new dump task name.

400

DIS.4357

Exceeded transfer task quota.

A maximum of five dump tasks can be created for one stream at the same time. Creating six dump tasks will exceed the quota limit.

Delete the discarded dump tasks and then add dump tasks again.

400

DIS.4358

The stream supports specific transfer tasks. Check the data type of the stream.

Common dump tasks cannot be created in the stream for small file dump.

Create a new stream and then dump tasks in the stream.

400

DIS.4360

Invalid data schema.

The data schema entered during stream creation or update is invalid.

Ensure that the data schema format is correct and try again.

400

DIS.4601

The number of resource tags has reached the maximum.

A resource has a maximum of 10 tags. Adding 11 tags will exceed the quota limit.

Delete the discarded tags and then add tags again.

400

DIS.4602

Invalid resource type.

The resource type is invalid.

Ensure that the resource type is valid.

400

DIS.4603

The resource does not exist.

The resource does not exist.

Ensure that the resource is not deleted.

400

DIS.4604

The key does not exist.

The tag key does not exist.

Ensure that the tag key exists.

400

DIS.4605

The action is not supported.

The current tag operation is not supported.

Ensure that the current tag operation is valid. Currently, only the create and delete operations are supported.

500

DIS.5000-DIS.5999

System error.

NOTE:

Contact technical support to handle system errors.

-

-