When an error occurs, OpenSearch returns an error code and an error message. Use the error code to identify the cause and apply the fix described in this reference.
Common errors
The following errors are frequently encountered. Each entry describes the cause and the recommended action.
| Error code | Description | Action |
|---|---|---|
| 1000 | Timeout error. | Retry the request. If the error persists, submit a ticket. |
| 2112 | A feature function in the sort expression — such as text_relevance(field) or fieldterm_proximity(field) — references a field that is not a source index field of the query. Search results are not affected. | Update the sort expression to reference a valid source index field. |
| 3007 | API operations for pushing data are called too frequently. | Reduce the rate at which you call data push API operations. |
| 4003 | Signature verification failed. | Use the sample document to verify that the same signature result is produced. If the signature is correct, check that common parameters (uppercase) are sorted before request parameters (lowercase) in alphabetical order, and that spaces are encoded correctly. For details, see the authorization documentation. |
| 4007 | Failed to parse JSON. The JSON field may contain unescaped double quotation marks (") or non-printable characters. | Escape the problematic characters or add a filter condition, then retry. |
| 4010 | The TimeStamp parameter format or value is invalid. | Set TimeStamp to the current time in the required format. |
| 5001 | The user does not exist. The AccessKey pair or the API endpoint may be invalid. | Verify your AccessKey pair and API endpoint. To find the API endpoint, log on to the OpenSearch console, go to Instance Management, find the application, click Details in the Actions column, and view the value in the API Endpoint section. |
| 5008 | The AccessKey pair is disabled. | Log on to the OpenSearch console and enable your AccessKey pair on the AccessKey management page. |
| 6013 | The sum of start and hit exceeds 5000. No results are returned. | Make sure start + hit ≤ 5000. For result sets larger than 5000, configure a scroll search. See the API reference for scroll search requirements. |
| 6015 | The request was discarded because the logical computing units (LCUs) of computing resources exceed the purchased quota. | Increase the quota: log on to the OpenSearch console, go to Instance Management, find the application, and choose More > Change Specifications/Quotas. |
| 6127 | The fields referenced in clauses other than query clauses must be configured as attribute fields. | Modify the application schema and add the required attribute fields using offline changes. For details, see Modify Offline Application. |
| 7500 | Internal error. | Submit a ticket. |
System errors (1000–1999)
| Error code | Description |
|---|---|
| 1000 | An internal error occurred. |
| 1001 | The template does not exist. |
| 1003 | The index type is invalid. |
| 1004 | The service is unavailable. Try again later. |
Application errors (2000–2999)
| Error code | Description |
|---|---|
| 2001 | The specified application does not exist. |
| 2002 | The specified application already exists. |
| 2003 | The number of applications has reached the upper limit. |
| 2004 | The application name is invalid. The name can be up to 30 characters and contain digits, letters, and underscores (_). |
| 2005 | The application name is not specified. |
| 2006 | The new application name is not specified. |
| 2007 | The description exceeds the maximum length of 300 characters. |
| 2008 | A summary parameter is invalid. |
| 2009 | Failed to update the application status. |
| 2010 | The application is paused. |
| 2011 | The application is frozen. |
| 2012 | The application is not started. |
| 2013 | The delete operation failed because the application does not exist. |
| 2014 | Failed to upload the file. |
| 2016 | The region is not specified. |
| 2017 | The application does not reside in the current region. |
| 2099 | This operation is unavailable. |
| 2101 | The expression does not exist. |
| 2102 | The expression name already exists. |
| 2103 | The number of expressions in the application has reached the upper limit. |
| 2104 | The expression name is invalid. The name can be up to 30 characters and contain digits, letters, and underscores (_). |
| 2105 | The expression name is not specified. |
| 2106 | The new expression name is not specified. |
| 2107 | The expression description exceeds the maximum length of 300 characters. |
| 2108 | The expression description format is invalid. |
| 2109 | The expression format is invalid. |
| 2110 | The expression exceeds the maximum length. |
| 2111 | The expression ID is not specified. |
| 2112 | The expression is invalid. |
| 2112 | The sort expression is invalid. |
| 2113 | The expression is empty. |
| 2114 | An operation error occurred. |
| 2201 | The rough sort expression name is not specified. |
| 2202 | The rough sort expression name already exists. |
| 2203 | The number of rough sort expressions exceeds the upper limit. |
| 2204 | The rough sort expression name is invalid. The name can contain only digits, letters, and underscores (_). |
| 2205 | The rough sort expression name exceeds the maximum length. |
| 2206 | The fields used for rough sort are not of numeric types. |
| 2207 | The rough sort expression does not exist. |
| 2208 | The rough sort expression is invalid. Make sure that fields are specified in the expression. |
| 2209 | The weight configuration in the rough sort expression is invalid. Weight values must be non-zero numbers in the range [-100000, 100000]. FLOAT values are precise to six decimal places. |
| 2210 | The name conflicts with the default rough sort expression name in the system. |
| 2211 | The parameter value in the timeliness() function is not of the INT type. |
| 2551 | The drop-down suggestion rule specified in the query does not exist. |
Document errors (3000–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 | The document format is invalid. |
| 3006 | The command used to process the document is invalid. |
| 3007 | Too many requests were submitted in a short period of time. |
| 3008 | The document size is too large. |
| 3009 | No document ID is specified. |
| 3011 | Pushing documents via API operations is not supported after an ApsaraDB RDS for MySQL or MySQL data source is configured. |
| 3012 | The specified resource does not exist. |
| 3013 | The document push rate exceeds the maximum threshold set for the application. |
| 3014 | The document push rate exceeds the system limit. |
| 3015 | The number of documents pushed per request exceeds the upper limit. |
| 3016 | The total number of documents in the application exceeds the upper limit. |
Authorization errors (4000–4999)
| Error code | Description |
|---|---|
| 4001 | Authentication failed. |
| 4002 | No signature is configured. |
| 4003 | Signature verification failed. |
| 4004 | The SignatureNonce parameter is not specified. |
| 4005 | The SignatureNonce value is not unique. |
| 4006 | SignatureNonce verification failed. |
| 4007 | Failed to parse JSON. |
| 4008 | No username is specified. Check that the domain name is correct. |
| 4009 | The user ID is not specified. |
| 4010 | The timestamp is invalid. |
| 4011 | This operation is not allowed for a demo account. |
| 4012 | The specified table does not exist. |
| 4013 | The timestamp format is invalid. |
| 4014 | The Timestamp parameter is not specified. |
| 4020 | RAM user authentication failed. |
User errors (5000–5999)
| Error code | Description |
|---|---|
| 5001 | The user does not exist. |
| 5002 | The username is invalid. |
| 5003 | You are not logged on. |
| 5004 | You have overdue payments. |
| 5005 | The OpenSearch service is not activated. Activate it on the Alibaba Cloud official website. |
| 5006 | The specified application is frozen due to overdue payments. |
| 5008 | The AccessKey pair is disabled. |
| 5009 | The user is deleted. |
| 5010 | The AccessKey pairs are disabled. |
| 5011 | Multiple users are registered with 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. |
Search errors (6000–6999)
| Error code | Description |
|---|---|
| 2022 | The application version is unavailable. Reindexing is not complete for this version. |
| 6001 | No search query is entered. |
| 6002 | The keyword used to search for a key is invalid. |
| 6003 | The keyword used to search for a field is invalid. |
| 6004 | Complex queries are not specified. |
| 6005 | The field is invalid. |
| 6006 | The request contains too many application names. |
| 6007 | The total number of indexes in each template for a multi-index query exceeds the upper limit. |
| 6008 | Failed to parse the request due to a syntax error. |
| 6009 | The query clause is too long. |
| 6010 | The rerank size is invalid. |
| 6011 | The SignatureNonce format is invalid. |
| 6013 | The sum of start and hit exceeds the upper limit. |
| 6014 | The request was discarded because the system is busy. |
| 6015 | The request was discarded because the LCUs of computing resources exceed the purchased quota. |
| 6016 | The request was discarded because the number of query hits exceeds the upper limit. The valid range is [0, 500]. |
| 6017 | The scroll parameter is specified, but search_type is not set to scan. |
| 6018 | The scroll parameter is specified, but search_type is not specified. |
| 6019 | Failed to parse the scroll_id parameter. |
| 6020 | The scroll parameter value is invalid. |
| 6021 | The aggregate, sort, or distinct clause is not supported in scroll requests. |
| 6022 | The scroll_id value has expired. |
| 6024 | The hit parameter value in the drop-down suggestion is invalid. |
| 6031 | The abtest parameter value is invalid. |
| 6033 | The re_search parameter value is invalid. |
| 6034 | The biz parameter value is invalid. |
| 6100 | No search query is specified. |
| 6101 | The index field referenced in the query does not exist. |
| 6102 | The numeric value range in the query clause is invalid. |
| 6103 | The return value of the expression in the filter clause is not of the BOOLEAN type. |
| 6104 | The return value of the expression in the sort clause is of the BOOLEAN type. |
| 6105 | The sort clause contains duplicate expressions. |
| 6106 | The query clause in the query is invalid. |
| 6107 | The return value of the statistical function is of the BOOLEAN or STRING type. |
| 6108 | The range in the statistical function is not in ascending order. |
| 6109 | The data type of the value returned by the range expression in the statistical function is invalid. |
| 6110 | The statistical function does not exist. |
| 6111 | The statistical function is invalid. |
| 6112 | The query clause is invalid. |
| 6113 | The filter clause is invalid. |
| 6114 | The aggregate clause is invalid. |
| 6115 | The sort clause is invalid. |
| 6116 | The distinct clause is invalid. |
| 6117 | The query contains unknown clauses. |
| 6118 | A syntax error occurred. |
| 6119 | The dist_count value in the distinct clause is invalid. This value must be an integer greater than 0. |
| 6120 | The dist_times value in the distinct clause is invalid. This value must be an integer greater than 0. |
| 6121 | The reserved parameter in the distinct clause is invalid. This parameter must be set to true or false. |
| 6122 | The distinct_key parameter is not specified in the distinct clause. |
| 6123 | The grade value in the distinct clause is invalid — for example, it is blank or set to a non-numeric value. |
| 6124 | The distinct value in the distinct clause is invalid. The value must be in the range (0, 2]. |
| 6125 | The max_item_count value in the distinct clause is invalid. This value must be an integer greater than 0. |
| 6126 | The update_total_hit parameter in the distinct clause is invalid. This parameter must be set to true or false. |
| 6127 | The request contains undefined attribute fields. Modify the application schema and try again. For details, see Modify Offline Application. |
| 6128 | The data types of the operands surrounding the binary operator in the expression are different. |
| 6129 | Both operands surrounding the binary operator in the expression are constants. |
| 6130 | The value type of the binary logic operation expression is invalid. The value must be of the BOOLEAN type. |
| 6131 | The values in the binary expression are of the STRING type, which is not supported. |
| 6132 | The values in the binary expression are of the ARRAY type, which is not supported. |
| 6133 | The value type of the bit manipulation is invalid. |
| 6134 | The data type of the value returned by the constant expression is invalid. |
| 6135 | The value type of the constant expression is invalid. |
| 6136 | The clause uses an invalid expression — for example, sort=-2, where -2 is a constant. |
| 6140 | A syntax error occurred in the aggregate clause. The SUM function does not support fields of the LITERAL type. |
| 6300 | The values in the constant expression are not integers or floating-point numbers. |
| 6301 | The operands for bitwise negation are not integers. |
| 6302 | The operands for negation are not numbers. |
| 6303 | The operands for the logical NOT operation are not numbers. |
| 6304 | The data type of the operand for the binary operation is invalid. |
| 6305 | The binary operator is invalid. |
| 6306 | The parameter type of the function is invalid. |
| 6307 | The function is undefined. |
| 6308 | The number of parameters in the function is invalid. |
| 6309 | The array operation is invalid. |
| 6310 | No field can be filtered. |
| 6311 | An array field is used as a single-value field. |
| 6312 | A single-value field is used as an array field. |
| 6313 | The subscript value of the array field is invalid. The subscript value must be greater than or equal to 0. |
| 6314 | The field type is invalid. |
| 6315 | The parameter that specifies an index field does not exist. |
| 6316 | No index is specified in the query. |
| 6317 | A formula is used more than once in the filter clause. Each formula can be used only once per filter clause. |
| 6318 | Failed to parse the formula syntax. |
| 6400 | The sort script does not exist. |
| 6450 | An error occurred while using the script. |
| 6500 | The search syntax references fields that do not exist. |
| 6501 | No index data is in the online system. |
| 6502 | The query syntax is invalid. |
| 6503 | The default operator OR is not supported. |
| 6504 | Accurate statistics are not supported. |
| 6505 | The rank size is invalid. |
| 6506 | Query analysis returned too many terms. |
| 6601 | An index field is included in more than one rule. Each index field can appear in only one rule. |
| 6602 | No search query is specified — for example, default:" is specified. |
| 6603 | The index field in the query is not specified in the query analysis rule. |
| 6604 | The keyword is not enclosed in single quotation marks — for example, default:xxx is specified. The correct form is default:'xxx'. |
| 6605 | The keyword is enclosed in double quotation marks ("). Query analysis rules cannot be configured in this case. |
| 6606 | The search query does not contain the index that needs to be analyzed. |
| 6607 | The disable parameter format is invalid. |
| 6608 | The index field to be disabled based on the disable parameter does not exist. |
| 6609 | The list of features to be disabled based on the disable parameter does not exist. |
| 6610 | The query returned by query analysis is empty. This may occur when the original query is empty or contains only stop words. |
| 6611 | No index field is specified in the query. |
| 6612 | The intervention data has not taken effect. |
Data processing errors (7000–7999)
| Error code | Description |
|---|---|
| 7202 | The command is invalid. Only UPDATE, ADD, and DELETE are supported. |
| 7301 | Failed to push data. The primary key field of the document does not exist. |
| 7302 | Data type mismatch. Failed to push data because the primary key value of the document is invalid. |
| 7303 | Failed to push data. The document contains multiple primary key values. |
| 7304 | Failed to push data. The primary key value of the document is empty. |
| 7305 | Failed to push data. The table name does not exist in the current application. |
| 7500 | An internal error occurred. Submit a ticket. |
| 7503 | Failed to push data. The JSON plug-in returned a field value that is not in JSON format. Check the value and retry. |
| 7504 | Failed to push data. The key corresponding to the field value returned by the JSON plug-in does not exist. |
| 7505 | A configuration error occurred in the TairLDBExtractor plug-in, causing the connection to Tair to fail. Check that the configuration ID and namespace are valid. |
| 7510 | Failed to push data. An error occurred in field processing by the KeyValueExtractor plug-in. |
| 7515 | An error occurred while applying the filter condition. |
| 7520 | Failed to push data. The single document size exceeds the system limit of 1 MB. |
| 7523 | Failed to push data. An error occurred in data processing by the StringConnector plug-in. |
| 7524 | The geo field value is outside the valid range. The longitude value must be greater than 180, and the latitude value must be greater than 90. |
| 7525 | The geo or range field format is invalid. |
| 7601 | An error occurred while the task was running. Submit a ticket. |
| 7602 | No data in the MaxCompute table. Make sure data is generated in the MaxCompute table partitions and retry. |
| 7603 | An error occurred while configuring an ApsaraDB RDS for MySQL or PolarDB for MySQL data source. |
| 7605 | A configuration error occurred in Taobao Distributed Data Layer (TDDL). |
| 7607 | You do not have permissions on the MaxCompute table. |
| 7608 | A source field does not exist in the MySQL data source. |
| 7803 | Failed to push data. The document to be updated does not exist. |
| 7805 | Failed to push data. An error occurred in data processing by the HTML plug-in. |
| 7807 | The field type and value do not match. The field type conversion failed and the missing value is imputed with a default value. |
| 73106 | The number of data push operations has reached the upper limit. Increase the quota. |
Document internal errors (8000–8999)
| Error code | Description |
|---|---|
| 8001 | Failed to save the error message. |
| 8002 | Required parameters are missing. |
| 8003 | The application does not exist. |
| 8004 | One or more parameters are invalid. |
Template errors (9000–9999)
| Error code | Description |
|---|---|
| 9001 | The username is not specified. |
| 9002 | The application name is not specified. |
| 9003 | The template name is invalid. The name can contain only digits, letters, and underscores (_). |
| 9004 | The template name exceeds the maximum length of 30 characters. |
| 9005 | An error occurred while querying the template information. |
| 9006 | The template name already exists. |
| 9007 | An error occurred while inserting data into the template. |
| 9008 | The data is invalid. |
| 9009 | The number of defined fields exceeds the system limit. |
| 9010 | The field name is reserved. |
| 9011 | The field name already exists. |
| 9012 | The index name does not meet the requirements. An index name can be up to 30 characters, must start with a letter, and can contain digits, letters, and underscores (_). Multi-value fields cannot be of the SWS_TEXT or TEXT type. |
| 9013 | Arrays are not supported. |
| 9014 | Primary keys are not supported. |
| 9015 | No primary key is specified. |
| 9016 | The primary key is not unique. |
| 9017 | Failed to update the information. |
| 9018 | Failed to delete the information. |
| 9019 | The number of search fields exceeds the upper limit. The maximum number of search fields that contain multiple index fields is four. |
| 9020 | An index field of the STRING or TEXT type is used in multiple single-field search fields. |
| 9021 | The index name does not meet the requirements. An index name can be up to 30 characters, must start with a letter, and can contain digits, letters, and underscores (_). |
| 9022 | This table is associated with another table. |
| 9023 | The index name references fields of different types, which is not allowed. |
| 9100 | An internal error occurred. |
| 9101 | The number of fields exceeds the upper limit. |
| 9102 | This data source is not in use. |
| 9103 | The connection to the secondary table is invalid. |
| 9104 | The number of association levels exceeds the upper limit of two. |
| 9105 | The template to be checked does not exist. |
| 9501 | The username is not specified. |
| 9502 | The application name is not specified. |
| 9519 | The template is not specified. |
| 9600 | An internal error occurred. |
| 9902 | The field type of the plug-in is invalid. |
| 9999 | This service is unavailable for this domain name. |
Data synchronization errors (10000 and above)
| Error code | Description |
|---|---|
| 10001 | Failed to get the TDDL information because the TDDL group key is not specified. |
| 10002 | Failed to get the field, or the table does not exist. |
| 10010 | Specific data sources contain invalid data. The invalid data is ignored. |
| 10011 | Failed to connect to Aggregator. |
| 10012 | The application contains documents. |
| 10013 | The application schema is not a custom one. |
| 10014 | The data source type is invalid. |
| 10100 | Failed to create the task. Specific tasks are in progress. |
| 10101 | The application ID is not specified. |
| 10102 | The action is invalid. |
| 10106 | The application ID is not specified. |
| 10107 | The application ID is not specified. |
| 10110 | The task is complete. |
| 10112 | The number of documents exceeds the upper limit. |
| 10201 | Failed to get the quota list. |
| 10202 | Failed to update the quota. |
| 10301 | One or more required parameters are not specified or have invalid formats. |
| 10302 | The time parameter is invalid. |
| 10303 | No data source is configured. |
| 10304 | The quota for this table exceeds the upper limit. |
| 10305 | An Object Storage Service (OSS) parameter is invalid. |
| 10306 | The OSS bucket name is invalid. |
| 10307 | The OSS record type is invalid. |
| 10308 | The logging feature of the OSS bucket is disabled. |
| 10309 | Specific tasks are in progress. |
| 10310 | The application is not running. Tasks cannot be created. |
| 10311 | The time range is invalid. |
| 10312 | The application description exceeds the maximum length of 600 characters. |
| 10313 | The OSS content format is invalid. |
| 10314 | Failed to access the access control list (ACL) in the region where the OSS bucket resides. |
| 10315 | The OSS bucket endpoint is invalid. |
| 10330 | Data source parameters are invalid. |
| 10350 | Failed to connect to the MaxCompute data source. |
| 10351 | An error occurred in the MaxCompute data source. |
| 10400 | The OSS bucket name prefix is invalid. |
| 10450 | The field does not exist. |
该文章对您有帮助吗？