If an error occurs, an error code and an error message are returned. The following sections describe the cause of each error to help you troubleshoot the errors that may occur during your use of OpenSearch.
Common errors
Error code | Description |
1000 | A timeout error occurred. Try again and check whether the error persists. If the error persists, submit a ticket. |
3007 | The interval at which API operations are called to push data exceeds the limit. We recommend that you call API operations at an appropriate interval. |
4003 | Use the sample document to check whether the same signature result is returned. This method can be used to check whether the error is caused by the signature algorithm. If the error is not caused by the signature algorithm, check whether the common parameters in uppercase rank before the request parameters in lowercase after all these parameters are sorted in alphabetical order. In addition, check whether encoding rules such as rules about spaces are followed. For more information, see the authorization documentation. |
4007 | Failed to parse the format because JSON fields contain double quotation marks (") or non-printable characters. In this case, escape the characters or specify a filter condition and try again. |
5001 | The user does not exist. Generally, this error occurs because the AccessKey pair or API endpoint is invalid. Make sure that the AccessKey pair and API endpoint are valid and try again. To view the API endpoint, perform the following operations: Log on to the OpenSearch console. In the left-side navigation pane, click Instance Management. Find the application that you want to manage and click Manage in the Actions column. In the API Endpoint section of the Instance Details page, view the API endpoint. |
5008 | OpenSearch verifies your identity by using the AccessKey pair. Make sure that your AccessKey pair is enabled. You can create or delete an AccessKey pair on the AccessKey Pair page of the Resource Access Management (RAM) console. |
7500 | An internal error occurred. Submit a ticket. |
System errors whose error codes range from 1000 to 1999
Error code | Description |
1000 | An internal error occurred. |
1001 | The template is not found. |
1004 | The service is unavailable. Try again later. |
Application-related errors whose error codes range from 2000 to 2999
Error code | Description |
2001 | The specified application is not found. |
2002 | The specified application already exists. |
2004 | Invalid application name. The application name can be up to 30 characters in length, and can contain digits, letters, and underscores (_). |
2005 | The application name is not specified. |
2006 | The new application name is not specified. |
2007 | The length of the description exceeds the upper limit. The description can be up to 300 characters in length. |
2009 | Failed to update the status of the application. |
2016 | The region is not specified. |
2017 | The application does not reside in the current region. |
2099 | This operation is unavailable. |
Document-related errors whose error codes range from 3000 to 3999
Error code | Description |
3001 | The document is empty. |
3002 | The document size exceeds the upper limit. |
3003 | The number of documents has reached the upper limit. |
3004 | Failed to save the document. |
3005 | Invalid document format. |
3006 | The command that is used to process the document is invalid. |
3007 | Excessive requests are submitted in a short period of time. |
3008 | The document size is excessively large. |
3009 | No document ID is specified. |
3012 | The specified resource is not found. |
3013 | The rate at which documents are pushed exceeds the maximum threshold specified in the application. |
3014 | The rate at which documents are pushed exceeds the system limit. |
3015 | The number of documents that are pushed each time exceeds the upper limit. |
3016 | The total number of documents in the application exceeds the upper limit. |
Authorization-related errors whose error codes range from 4000 to 4999
Error code | Description |
4001 | The authentication failed. |
4002 | No signature is configured. |
4003 | The signature failed the verification. |
4004 | The SignatureNonce parameter is required. |
4005 | The value of the SignatureNonce parameter is not unique. |
4006 | The SignatureNonce verification failed. |
4007 | Failed to parse the JSON format. |
4008 | No username is specified. Check whether the domain name is correct. |
4009 | The user ID is not specified. |
4010 | Invalid timestamp. |
4011 | This operation is not allowed for a demo account. |
4020 | The RAM user failed to be authenticated. |
User-related errors whose error codes range from 5000 to 5999
Error code | Description |
5001 | The user is not found. |
5002 | Invalid username. |
5003 | You have not logged on. |
5008 | The AccessKey pair is disabled. |
5100 | You are not authorized to perform operations in this region. |
5004 | You have overdue payments. |
5005 | The OpenSearch service is not activated. Go to the Alibaba Cloud official website to activate the service. |
5006 | The specified application is frozen due to overdue payments. |
5008 | The AccessKey pair is disabled. |
5009 | The user is deleted. |
5010 | The AccessKey pair is disabled. |
5011 | Multiple users are registered by using the same email address. |
5012 | CODE_USER_ALIYUN_USER_ID_INVALID. No error message is returned. |
5013 | CODE_USER_ALIYUN_BID_INVALID. No error message is returned. |
5014 | CODE_USER_CLIENT_ID_INVALID. No error message is returned. |
5015 | CODE_USER_ID_INVALID. No error message is returned. |
5100 | You are not authorized to perform operations in this region. |
Data processing errors whose error codes range from 7000 to 7999
Error code | Description |
7202 | Invalid command. Only UPDATE, ADD, and DELETE commands are supported. |
7301 | The primary key field of the document is not found. Failed to push the data because the primary key value of the document is not found. |
7302 | The data type does not match. Failed to push the data because the primary key value of the document is invalid. |
7303 | The document contains multiple primary key values. Failed to push the data because multiple primary key values are contained in the document. |
7304 | The primary key value of the document is empty. Failed to push the data because the primary key value of the document is empty. |
7305 | Table data that does not belong to the application is pushed. Failed to push the data because the table name does not exist in the current application. |
7500 | An internal error occurred. Submit a ticket. |
7520 | Failed to push the data because the size of a single document exceeds 1 MB, which is the upper limit specified by the system. |
7503 | Failed to push the data because the field value that is obtained by using the JSON plug-in is not in the JSON format. Check and try again. |
7504 | Failed to push the data because the key corresponding to the field value that is obtained by using the JSON plug-in does not exist. |
7515 | An error occurs when the filter condition is being used. |
73106 | The number of data push operations has reached the upper limit. Increase the quota. |
7620 | An execution timeout error occurred for the data source query. |