TcaplusDB Error Codes
TcaplusDB Error Codes
| Error code | Description | Details | Shared or not | Solution |
|---|---|---|---|---|
| 2309 | TXHDB_ERR_RECORD_IS_NOT_SET_TTL | The record has no TTL set | N | It is a single-record expiration-related error. The record has no TTL set and requires the project team to check the SetTTL |
| 261 | TXHDB_ERR_RECORD_NOT_EXIST | The record does not exist | Y | The record does not exist. The app needs to check whether it meets the expectation |
| -256 | It usually occurs when calling RegisterTable, please check: 1. Whether the table parameters corresponding to the RegisterTable have been successfully added and approved (common tables do not exist or have been applied for but have not been approved); 2. If the dir is configured with a domain name, please check whether the domain name can be correctly resolved; 3. Please check whether the telnet(curl) dir_ip dir_port is successful, that is, whether the network link is OK (in the past, there have been many cases where the network access across IDC and DEV was not available). | |||
| -261 | TXHDB_ERR_INVALID_ARGUMENTS | Internal parameter error | N | |
| -273 | PROXY_ERR_INVALID_PARAMS | Internal parameter error | N | |
| -275 | API_ERR_OVER_MAX_KEY_FIELD_NUM | It indicates that the maximum number of keys has been exceeded. Currently, there are up to 8 keys and 7 list tables. If the API version is older, it is recommended to upgrade to the latest version of 3.46.0 | Y | 1. If the number of keys exceeds the limit, it will be blocked when adding a table through the page. 2. Generally, this error occurs in the setkey interface. Please check the number of setkey calls and whether the number of keys exceeds the limit |
| -279 | DIR_ERR_SIGN_FAIL | Password Error | N | Password Error, please check if the business password is correct |
| -517 | TXHDB_ERR_INVALID_MEMBER_VARIABLE_VALUE | Internal parameter error | N | |
| -525 | SVR_ERR_FAIL_TIMEOUT | 1. If the api initialization fails, this error will be returned, indicating that the connection to tcapdir or tcaproxy timed out; Please check: (1) If the dir is configured with a domain name, please check that the domain name can be correctly resolved; (2) Please check whether the telnet(curl) dirip dir_port is successful, that is, the network link is OK (in the past, there are many cases where the network access across IDC and DEV is not available); (3) If the proxy connection times out, you can contact DBA or Tcaplus Helper troubleshooting; 2. If a -525 error is returned, it is generally returned in a batch response package. At this time, you can first check whether the error continues to be reported: (1) If it only occurs occasionally, it may be caused by network fluctuations; (2) If it continues to occur, you can contact DBA or Tcaplus_Helper troubleshooting; | Y | 1. It indicates that the gameseverer's connection to tcaproxy timed out. Please check: (1) Whether the Tcaplus API and tcaproxy versions meet the Tcaplus API version number < = tcaproxy version number < = tcapsvr version number; (2) Whether the number of TCP connections of tcaproxy is within the limit; 2. If the tcaproxy returns a -525 error response package, it generally occurs only in batch requests. The reason is that tcapsvr does not return the response packet within the timeout period. In this case: (1) Find the tcaproxy that returns -525 error, and there will be error log. (2) Find the tcapsvr that returns the record timeout and confirm whether there is any problem with the performance of tcapsvr; |
| -529 | PROXY_ERR_NO_NEED_ROUTE_BATCHGET( )_ACTION_MSG_WHEN_NODE_IS_IN_SYNC_STATUS | It indicates that some commands in the lossy relocation are not supported. Currently, most of them are lossless relocations, and this error code will not be reported | N | This error code will be returned if the command words related to "xxxbypartkey" and "delete" are not supported during lossy relocation. |
| -531 | API_ERR_OVER_MAX_VALUE_FIELD_NUM | It indicates that the number of value fields exceeds the limit. The limit number of generic tables is 128, and the limit number of List tables is 127. The 3.46.0 version increased the limit of generic tables to 256 and list tables to 255 | Y | Check whether the number exceeds the limit according to the version. If it exceeds the limit, you can download the latest version and upgrade it |
| -773 | TXHDB_ERR_ALREADY_OPEN | The engine file is opened repeatedly | N | |
| -781 | SVR_ERR_FAIL_SHORT_BUFF | It indicates that the buf is too short, and it is an internal error | N | |
| -785 | PROXY_ERR_NO_NEED_ROUTE_WHEN( )_NODE_IS_IN_REJECT_STATUS | It indicates that some commands in the lossy relocation are not supported. Currently, most of them are lossless relocations, and this error code will not be reported | N | |
| -787 | API_ERR_OVER_MAX_FIELD_NAME_LEN | It indicates that the field name size exceeds the limit (32 B) | Y | If the field name exceeds the limit, it will be blocked when adding a table through the page. You can change the length of the field name |
| -1037 | SVR_ERR_FAIL_SYSTEM_BUSY | It indicates that the storage layer is overloaded. You can contact DBA or Tcaplus_Helper troubleshooting. Common causes: 1. The app access is large, and the storage layer is overloaded 2. The storage layer disk performance is abnormal, resulting in overloading 3. The process is stuck, and the ago log is generated | Y | 1. Confirm whether there is a problem with tcapsvr's performance, such as disk performance or CPU usage; 2. If there is no problem with the performance, confirm whether the main thread is stuck, and search the ago log; 3. Search the worker thread log to see if there is a log with the slow keyword, indicating that processing a request takes more than 200 ms; |
| -1043 | API_ERR_OVER_MAX_FIELD_VALUE_LEN | 1. The field value length exceeds the limit in the table definition, such as the definition of string100B. This error is returned when the value is actually written to 101B 2. The content of a single key field exceeds 1024 | Y | 1. Check whether the field buf exceeds the limit according to the table definition 2. Update the table and check whether the local table meta is updated 3. Check whether the key field content exceeds 1024 |
| -1293 | SVR_ERR_FAIL_RECORD_EXIST | The record of insert already exists | Y | |
| -1299 | API_ERR_FIELD_NOT_EXSIST | The accessed field does not exist. Please confirm that the field name is spelled correctly | Y | |
| -1303 | DTR_ERR_APP_IS_NOT_FOUNT | dir can not found app | Y | 1.Check if the app id is correct 2.Check if the dir address is correct |
| -1310 | TableNotExist | Table does not exist | N | Please check on the business side if the table exists or if the table addition has been completed |
| -1050 | TCAPLUS_INDEX_ERR_SEND_TO_INDEX_SERVER_FAILED_FOR_NO_CONNECTOR | global index query failed | Y | Check if global indexing is configured |
| -1549 | SVR_ERR_FAIL_INVALID_FIELD_NAME | The accessed field does not exist. Please confirm that the table structure has been updated to the back-end | Y | It indicates that the field being accessed is illegal: 1. Check whether the field name is correct; 2. Confirm that the table structure has been locally updated but has not changed on the Tcaplus system; 3. You can contact the DBA or Tcaplus_Helper to search for the field name in the background log. |
| -1555 | API_ERR_FIELD_TYPE_NOT_MATCH | It indicates that the data type of the field value does not match its definition type. For example, the type of a Key field is int8, and when trying to call GetKeyFloat to get the value of this field, it is recommended to check the table definition and confirm the field data type. | Y | |
| -1792 | GEN_ERR_TABLE_READONLY | It indicates that the table is in read-only mode. Please check whether the RCU, WCU, or capacity exceeds the threshold set by the user. | Y | It may occur more in Tencent cloud mode, mainly because the QPS of the table set by the project team is lower than the actual value. |
| -1805 | SVR_ERR_FAIL_VALUE_OVER_MAX_LEN | The record exceeds the maximum length, and cannot exceed 10 MB after serialization | Y | For non-list tables, confirm whether the record exceeds the maximum length set for a single field. For list tables, confirm the maximum number of elements under a single key defined in the table |
| -1811 | API_ERR_PARAMETER_INVALID | It indicates a parameter error return. It is usually an unreasonable return of parameters set in the interface of an api call | Y | 1 Refer to the .h comment of the interface to check whether the parameters are set correctly. 2 Provide the interface and parameters, and contact tcaplus to help locate the problem |
| -2048 | GEN_ERR_TABLE_READ_DELETE | It indicates that the capacity exceeds the limit, which can be read and deleted but cannot be written | Y | It may occur more in Tencent cloud mode, mainly because the QPS of the table set by the project team is lower than the actual value. |
| -2061 | SVR_ERR_FAIL_INVALID_FIELD_TYPE | Table field type error | Y | The project team should determine whether the table XML used by gameserver and Tcaplus is consistent. The character type is illegal, including: 1. The length of the set field is not equal to the length of the field in the table definition. For example, the length of the field must be 4 for the int type; 2. Unsupported field type; The project team should first check whether the table xml used by gamesvr and tcaplus is consistent |
| -2067 | API_ERR_OPERATION_TYPE_NOT_MATCH | 1. The table type and command word do not match. For example, the generic table uses the command word of list table 2. The flag bit does not support the command. For example, SetLimit and SetFlag do not match the command | Y | 1. The table type and command word do not match. Determine whether the list and generic table commands are used incorrectly 2. The flag bit set by request does not support the current command. This error can be ignored |
| -2304 | GEN_ERR_ACCESS_DENIED | Access denied error | N | This is because the actual read and write volume of the table exceeds the specified QPS. Confirm whether the QPS is specified when adding the table. If the problem has not been solved, please contact the administrator. |
| -2317 | SVR_ERR_FAIL_SYNC_WRITE | tcapsvr_fail_sync_write | N | |
| -2323 | API_ERR_PACK_MESSAGE | Packaging failed while setting data | Y | Confirm whether the local table meta is consistent with the online table. You can check the tdr packaging rules, or contact tcaplus to help locate the problem |
| -2560 | GEN_ERR_INVALID_ARGUMENTS | Parameter error, please contact the administrator | N | If it is a ServiceAPI error, there will be an error log. The back-end communication module will not pass this error to ServiceAPI. If yes, please contact the administrator |
| -2573 | SVR_ERR_FAIL_WRITE_RECORD | Write engine error, please contact the administrator | Y | 1. Check whether a single engine file exceeds 256 GB; 2. Whether the disk is abnormal, such as read-only or bad track; 3. Check the specific log for more detailed error information; |
| -2583 | DIR_ERR_IS_NOT_THIS_ZONE_API | Dir address error | N | Please check whether the dir address configuration and corresponding zone are correct |
| -2579 | API_ERR_UNPACK_MESSAGE | Response message unpacking failed when GetData | N | Troubleshoot tdr unpacking rules Whether the local table meta is consistent with the online table Whether SetKey/SetValue and SetData are mixed |
| -2816 | GEN_ERR_UNSUPPORT_OPERATION | Unsupported operation, please contact the administrator | Y | Some functions are not supported for some command words List tables do not support setting and getting ttl List tables do not support setting and getting ttl For conditional query and update, the command words it supports only include (TCAPLUS_API_GET_REQ、TCAPLUS_API_GET_BY_PARTKEY_REQ、TCAPLUS_API_REPLACE_REQ、TCAPLUS_API_UPDATE_REQ、TCAPLUS_API_DELETE_REQ、TCAPLUS_API_PB_FIELD_INC_REQ、TCAPLUS_API_PB_FIELD_GET_REQ、TCAPLUS_API_UPDATE_ITEM_REQ、TCAPLUS_API_LIST_GETALL_REQ、TCAPLUS_API_LIST_DELETE_BATCH_REQ、TCAPLUS_API_LIST_REPLACE_REQ、TCAPLUS_API_LIST_GET_REQ、TCAPLUS_API_LIST_DELETE_REQ) The command words supported by the PB table only include (tcaplusdb::Head_TypeCmd_DATA_CMD_ADD_REQ、tcaplusdb::Head_TypeCmd_DATA_CMD_GET_REQ、tcaplusdb::Head_TypeCmd_DATA_CMD_DELETE_REQ、tcaplusdb::Head_TypeCmd_DATA_CMD_UPDATE_REQ、tcaplusdb::Head_TypeCmd_DATA_CMD_REPLACE_REQ、tcaplusdb::Head_TypeCmd_DATA_CMD_INDEXGET_REQ、tcaplusdb::Head_TypeCmd_CTRL_CMD_CMP_TABLE_META_REQ、tcaplusdb::Head_TypeCmd_CTRL_CMD_LIST_TABLE_META_REQ) When the PB protocol API calls SetMessageOption, it is invalid if setting MESSAGE_OPTION_MESSAGE_INVALID or MESSAGE_OPTION_MESSAGE_INVALID |
| -2823 | ENG_ERR_ENGINE_ERROR | Engine error, please contact the administrator | N | |
| -2829 | SVR_ERR_FAIL_DELETE_RECORD | Failed to delete the engine record. Please contact the administrator | N | If the record fails to be deleted, check the disk bad track on the hardware |
| -3072 | GEN_ERR_NOT_ENOUGH_MEMORY | The memory is not enough | N | If it is a ServiceAPI error, there will be an error log. Other modules will not pass this error to ServiceAPI. If yes, please contact the administrator |
| -3079 | ENG_ERR_DATA_ERROR | Data error, please contact the administrator | N | |
| -3085 | SVR_ERR_FAIL_DATA_ENGINE | The SetFieldName operation specified wrong field | Y | This error code mainly occurs when reading records and contains a wide range of error types, such as: (1) when xxxbypartkey, confirm whether the key field is set in SetFieldNames and whether the set value field is legal; (2) deserialization failure; (3) insufficient memory; (4) locking failure; (5) hash bucket reading failure, etc; Therefore, log in to the svr machine to view the specific error details; |
| -3091 | API_ERR_OVER_MAX_RECORD_NUM | Api failed to insert the record into the route, which generally does not occur. If it occurs, please contact tcaplus for troubleshooting | N | |
| -3328 | GEN_ERR_NOT_SATISFY_INSERT_FOR_SORTLIST | SortList table storage engine internal error, please contact Tcaplus_Helper for troubleshooting | N | Internal Meta maintenance error Sorting failed It does not belong to the situation that the sortlist table element is full and meets the expiration rules of sortlist, but the expiration fails |
| -3341 | SVR_ERR_FAIL_RESULT_OVERFLOW | The field value size exceeds the limit of its defined type | Y | Ask the project team whether it meets the expectations. It belongs to normal app logic. For example, some project teams will set the maximum and minimum values according to the logic |
| -3347 | API_ERR_INVALID_COMMAND | The command of the response package does not match | N | Possible reasons are as follows: 1. The command word not supported by the current interface is set in the request; 2. Some functions in the request and response object can only be called when a specific command word is used. If it is not used properly, this error will also be reported. For example, the response. GetTableRecordCount function can only be called when the current command word is TCAPLUS_API_GET_TABLE_RECORD_COUNT_RES. |
| -3603 | API_ERR_NO_MORE_RECORD | When FetchRecord, there is no record in the response package | Y | It is generally recommended that the project team judge GetResult first, then GetRecordCount, and then, for the loop FetchRecord. |
| -3859 | API_ERR_OVER_KEY_FIELD_NUM | It indicates that the maximum number of keys is exceeded. Currently, the maximum number of keys is 8, and for the list table, it is 7 | Y | 1. If the number of keys exceeds the limit, it will be blocked when adding a table through the page. 2. Usually, this error occurs on the setkey interface. Check whether the number of setkey calls exceeds the threshold. |
| -4109 | SVR_ERR_FAIL_INVALID_INDEX | The subscript of list data type element exceeds the range | Y | The app needs to check whether the idx passed is incorrect. Generally, the idx returned by listgetall is recommended as the idx for the next operation |
| -4115 | API_ERR_OVER_VALUE_FIELD_NUM | It indicates that the number of value fields exceeds the limit. The limit number of generic tables is 128, and the limit number of List tables is 127. The 3.46.0 version increased the limit of generic tables to 256 and list tables to 255 | Y | Check whether the number exceeds the limit according to the version. If it exceeds the limit, you can download the latest version and upgrade it |
| -4365 | SVR_ERR_FAIL_OVER_MAXE_FIELD_NUM | It indicates that the maximum number of fields is exceeded | Y | Confirm the number of supported fields according to the Tcaplus API version |
| -4371 | API_ERR_OBJ_NEED_INIT | 1. The API calls the database without initialization. 2. The table to be operated is not registered | Y | 1. Confirm whether the table has been added 2. After adding the table, whether the API side RegisterTable has been added 3. When the gameserver deletes the table during operation and adds a new table, it needs to re-register the table |
| -4621 | SVR_ERR_FAIL_MISS_KEY_FIELD | The request is missing a primary key field or index field | Y | |
| -4627 | API_ERR_INVALID_DATA_SIZE | The data size is incorrect, which is usually because the user's local table definition is inconsistent with the server. It is recommended to check: 1. Tcaplus background 2. The .h.cpp of the table compiled by the app 3. The tdr file of the table loaded when the app is started | Y | The app needs to confirms that whether the data size is incorrect. It is recommended to check whether the local table definition is consistent with the server table definition, and then check whether the request parameters set by the app code exceed the limit The specific reasons may be as follows: 1. The length of the target table name set in the request exceeds the limit (32); 2. The length of user data set in the request exceeds the limit (1024); 3. The size of the Key field value set in the request exceeds the limit (1024 B); 4. The size of the requested neutral performance test data exceeds the limit (256 B); 5. The size of the field value in the request exceeds the maximum size of the field value defined in the table definition; 6. The sum of the values of all fields specified in the Batch request exceeds the limit (10300000 B). |
| -4633 | COMMON_ERR_INVALID_ARRAY_INDEX | An invalid array index, such as when querying a specific field with "array_fields[10]" to retrieve the element at index 10, will result in an error if the array size is less than 11. | Y | Check if the index is valid, whether it exceeds the size of the array, and if the corresponding field is of array type. |
| -4883 | API_ERR_INVALID_ARRAY_COUNT | Invalid array size | Y | It means that "refer" in the table definition is greater than the "count", and the app needs to check it |
| -4889 | COMMON_ERR_INVALID_FIELD_NAME | Invalid field name | N | Please check if the local table definition and online table definition fields are consistent |
| -5137 | PROXY_ERR_PACK_MSG | Failed to package | N | |
| -5139 | API_ERR_INVALID_UNION_SELECT | Invalid union select | Y | In the Union definition, the data corresponding to select needs to exist. If it does not exist, an error will be reported |
| -5145 | COMMON_ERR_INVALID_EXPR_TYPE | Typically, errors occur during conditional filtering or updates when there is a mismatch in data types, such as when the condition "name > 10" requires the 'name' field to be of a numerical type. | Y | Check the data type defined in the table, and whether the types of values on both sides of numerical comparisons or assignments match. |
| -5393 | PROXY_ERR_SEND_MSG | Failed to send the message | Y | There are many reasons for this problem. Solve this problem according to the log on tcaproxy |
| -5395 | API_ERR_MISS_PRIMARY_KEY | Missing primary key in request | Y | It is recommended to check the app code to confirm whether all primary key field values are set for the request. |
| -5649 | PROXY_ERR_ALLOCATE_MEMORY | The memory is not enough | Y | It may be that the memory configured for transaction-type operations (including batch operations such as batchget) has reached the upper limit. Small probability is the other cause of out of memory |
| -5651 | API_ERR_UNSUPPORT_FIELD_TYPE | Field types not supported by PB, such as repeat type | N | Please check the type of pb and restproxy fields |
| -5905 | PROXY_ERR_PARSE_MSG | Failed to parse the message | N | Tcaproxy unpacking failed. Please check the problem according to the actual situation |
| -5907 | API_ERR_ARRAY_BUFFER_IS_SMALL | The memory is too small | N | |
| -6157 | SVR_ERR_FAIL_LIST_FULL | The number of list table elements exceeds the defined range. Please set element expiration | Y | |
| -6161 | PROXY_ERR_INVALID_MSG | Invalid message | N | Generally, the client will not return this error code. If tcaproxy has this log, it may be a security scan |
| -6412 | SVR_ERR_FAIL_LOW_VERSION | Low version | N | |
| -6417 | PROXYERR_FAILED_PROC_REQUEST( )BECAUSE_NODE_IS_IN_SYNC_STASUS | Some commands are not supported for lossy relocation. Currently, it is mainly lossless relocation, so this problem will not occur | Y | |
| -6669 | SVR_ERR_FAIL_HIGH_VERSION | High version | Y | The version of Tcaplus API is higher than that of tcaproxy |
| -6673 | PROXY_ERR_KEY_FIELD_NUM_IS_ZERO | No key field | Y | The app needs to check the app code |
| -6925 | SVR_ERR_FAIL_INVALID_RESULT_FLAG | Result_flag setting error, please refer to the result_flag description in the SDK | Y | |
| -6929 | PROXY_ERR_LACK_OF_SOME_KEY_FIELDS | Missing key fields in the request | Y | |
| -7181 | SVR_ERR_FAIL_PROXY_STOPPING | The proxy is stopping, and the app does not need to care about it. API or automatically switch to a new access layer | N | Only occurs when tcaproxy exits safely |
| -7185 | PROXY_ERR_FAILED_TO_FIND_NODE | Failed to find the node. Please contact the administrator | N | The routing node cannot be found, or the table may be deleted. Please contact the administrator |
| -7437 | SVR_ERR_FAIL_SVR_READONLY | The svr is read-only. It is usually because the disk is full or is in the process of master/slave switching | Y | (1) If it only occurs very briefly, the project team does not need to care about it; (2) If it continues to appear, contact DBA or Tcaplus_Helper; |
| -7441 | PROXY_ERR_INVALID_COMPRESS_TYPE | Invalid compression type | N | Currently, the snappy is supported |
| -7443 | API_ERR_INCOMPATIBLE_META | Incompatible meta. Please check whether the local table structure and the server table structure are compatible. | Y | Confirm that the version number of the table definition format used by gameserver is less than or equal to the table definition format used by Tcaplus. It is recommended to check whether the client table definition and the server table definition are compatible. 1. Check whether the version number of the table definition used by the client is less than or equal to the server's table definition, and check whether the version number of the table definition used by the client must be less than or equal to the server's table definition; 2. Confirm that the client has changed the table definition of the server to the corresponding or higher version before using the table definition of the higher version. |
| -7669 | API_ERR_PACK_ARRAY_DATA | Failed to package the array when setting data | Y | Check whether the refer setting of the array is correct and whether the count exceeds the limit; Whether the local table meta is consistent with the online table |
| -7693 | SVR_ERR_FAIL_SVR_READONLY( )_BECAUSE_IN_SLAVE_MODE | The request is sent to the svr slave node, which may be in the process of master/slave switching. If the error code is returned for a long time, please contact the administrator | Y | This error indicates that the master/slave switch is lossy and needs to be followed up |
| -7697 | PROXY_ERR_REQUEST_OVERSPEED | The request speed exceeds the limit | Y | This problem occurs frequently in Tencent Cloud mode because the QPS set by the project team is lower than the actual QPS used |
| -7949 | SVR_ERR_FAIL_INVALID_VERSION | Please check the optimistic lock to determine whether the requested record version number is inconsistent with the actual record version number | Y | Multiple requests are being written, but only one request is set to write successfully, so other requests report errors. The project team should confirm the requirements: 1. N requests, N successful writes, this does not need optimistic locks. 2. N requests, the first write succeeds, and the rest fail. This requires optimistic locks |
| -7953 | PROXY_ERR_SWIFT_TIMEOUT | Proxy timeout | Y | In the batchget scenario, if the tcaproxy -->tcapsrv -->tcaproxy is greater than 1 s, you need to follow up this problem and ask the project team app zone for help |
| -7955 | API_ERR_PACK_UNION_DATA | Failed the package the union when setting data | N | Confirm whether the local table meta is consistent with the online table. You can check the tdr packaging rules, or contact tcaplus to help locate the problem |
| -8205 | SVR_ERR_FAIL_SYSTEM_ERROR | Svr internal error, please contact the administrator | N | |
| -8209 | PROXY_ERR_SWIFT_ERROR | Proxy transaction non-timeout error, please contact the administrator | N | |
| -8211 | API_ERR_PACK_STRUCT_DATA | Failed the package the struct when setting data | Y | Confirm whether the local table meta is consistent with the online table. You can check the tdr packaging rules, or contact tcaplus to help locate the problem |
| -8461 | SVR_ERR_FAIL_OVERLOAD | The svr is overloaded, please contact DBA or Tcaplus_Helper | N | When the main thread forwards the request to the worker thread, the forwarding fails because the message queue is full. The common reasons are as follows: (1) The processing of the worker thread is slow. Confirm whether the worker thread has a slow log; (2) Whether the disk performance reaches the bottleneck; |
| -8465 | PROXY_ERR_DIRECT_RESPONSE | The proxy directly returns packets, which is equivalent to not going through the app logic, and is usually used to test APIs | N | |
| -8467 | API_ERR_UNPACK_ARRAY_DATA | Failed to unpack the array when GetData | Y | Check the tdr unpacking rules, including whether the refer is correct, whether the count exceeds the limit of the local table Whether the local table meta is consistent with the online table Whether the SetKey/SetValue and SetData are mixed |
| -8717 | SVR_ERR_FAIL_NOT_ENOUGH_DADADISK_SPACE | The datadisk space is not enough | Y | |
| -8721 | PROXY_ERR_INIT_TLOG | Failed to initialize the log module | N | |
| -8723 | API_ERR_UNPACK_UNION_DATA | Failed to unpack the union when GetData | Y | Check the tdr unpacking rules, including whether the selector of union is correct Whether the local table meta is consistent with the online table Whether the SetKey/SetValue and SetData are mixed |
| -8973 | SVR_ERR_FAIL_NOT_ENOUGH_ULOGDISK_SPACE | The ulogdisk space is not enough | Y | Delete the invalid files on the disk where the Ulog is located to reduce the disk occupation |
| -8979 | API_ERR_UNPACK_STRUCT_DATA | Failed to unpack the struct when GetData | Y | Troubleshoot tdr unpacking rules Whether the local table meta is consistent with the online table Whether SetKey/SetValue and SetData are mixed |
| -9233 | PROXY_ERR_REQUEST_ACCESS_CTRL_REJECT | Proxy access denied error | N | |
| -9235 | API_ERR_INVALID_INDEX_NAME | The local index does not exist | Y | Check the local index definition. Possible reasons are: 1 The index name passed in when constructing the request is NULL or an empty string; 2. The index name passed in when constructing the request is not defined in the metadata of the table. |
| -9485 | SVR_ERR_FAIL_UNSUPPORTED_PROTOCOL_CMD | Unsupported command word | N | |
| -9489 | PROXYERR_NOT_ALL_NODES_ARE_IN( )NORMAL_OR_WAIT_STATUS | The traversal request returns this error code because the table is in the relocation state | N | Currently using lossless relocation mode, this error code is rarely encountered |
| -9491 | API_ERR_MISS_PARTKEY_FIELD | Missing partkey field | N | The index field is missing in the request (such as get by part key request, delete by part key request, etc.). It is recommended to check the app code to confirm whether the index field values of all target local indexes are set for the request. The project team needs to check the code |
| -9745 | PROXY_ERR_ALREADY_CACHED_REQUEST_TIMEOUT | The cache request timed out when changing the route | Y | If this problem is encountered, it indicates that it is lossy and needs to be followed up continuously |
| -9747 | API_ERR_ALLOCATE_MEMORY | Failed to allocate the memory | N | It is recommended to check the memory usage of the client to ensure that there is enough memory for the SDK. |
| -9997 | SVR_ERR_FAIL_MERGE_VALUE_FIELD | Failed to merge the value field. It is an internal error, please contact the administrator | N | Second-level fields and fields above will have compatibility problems. At present, this feature is not enabled |
| -10001 | PROXY_ERR_FAILED_TO_CACHE_REQUEST | The cache request failed when changing the route | N | The request cache fails, usually because the cache is full |
| -10253 | SVR_ERR_FAIL_CUT_VALUE_FIELD | Failed to merge the value field. It is an internal error, please contact the administrator | N | |
| -10257 | PROXY_ERR_NOT_EXIST_CACHED_REQUEST | The cache request does not exist when changing the route | N | The request has not been cached in the cache |
| -10259 | API_ERR_MISS_BINARY_VERSION | Internal error, the version is missing in the binary field | N | For SetData/GetData, the binary field must have the version number 2B in front of it |
| -10509 | SVR_ERR_FAIL_PACK_FIELD | Internal error, field packaging failed, please contact administrator | N | |
| -10513 | PROXY_ERR_FAILED_NOT_ENOUGH_CACHE_BUFF | The cache buff is not enough when changing the route | N | It is due to insufficient memory |
| -10765 | SVR_ERR_FAIL_UNPACK_FIELD | Svr unpacking failed | N | |
| -10769 | PROXY_ERR_FAILED_PROCESS_CACHED_REQUEST | The proxy failed to process the cache request | N | The request is already cached, and another request will report this error |
| -10771 | API_ERR_INVALID_RESULT_FLAG | Invalid result flag | Y | |
| -11021 | SVR_ERR_FAIL_LOW_API_VERSION | The api version is too low, please upgrade the api | N | |
| -11027 | API_ERR_OVER_MAX_LIST_INDEX_NUM | The number of records for batch operation exceeds the limit. A maximum of 1024 records are supported | N | Reduce the number of records for batch operations |
| -11277 | SVR_ERR_COMMAND_AND_TABLE_TYPE_IS_MISMATCH | The method for operating the table does not exist | Y | The request command word does not match the table type. For example, the ListReplace request applies only to the list table, but is used to operate the generic table; |
| -11283 | API_ERR_INVALID_OBJ_STATUE | Not initialized, usually in a traversal request | N | The project team needs to check the code. At present, the main problem is the status error of the traverser, such as the traverser is not initialized. When calling the interface of the traverser, it will check whether the current status of the traverser is correct. For example, when calling the Start function, the current traverser is required to be in the READY status. |
| -11533 | SVR_ERR_FAIL_TO_FIND_CACHE | No data shard in the svr, internal error, please contact the administrator | N | The data shards do not exist. Check the specific log, such as whether the data shards accessed in the request have been deleted |
| -11537 | PROXY_ERR_SWIFT_SEND_BUFFER_FULL | the send buffer is full and the API processing response is too slow | Y | Follow up on the situation of the package receiving code of the gameserver calling the Tcaplus API |
| -11539 | API_ERR_INVALID_REQUEST | Invalid request | N | Possible reasons are as follows: 1. Illegal requests, such as Get requests that do not specify the Key of the record. It is recommended to check whether the request is legal by referring to the user documentation; 2. The request called by the Restful interface lacks the necessary Header. There is a detailed prompt in ErrMsg. It is recommended to check whether the Restful request is legal; 3. For scenarios such as transaction failure created by proxy for batch operation, contact the DBA to confirm the reason of the problem. |
| -11789 | SVR_ERR_FAIL_TO_FIND_META | The svr failed to find the table definition, internal error, please contact the administrator | Y | The table metadata does not exist. Check the specific log, such as whether the table accessed in the request has been deleted |
| -11793 | PROXY_ERR_REQUEST_OVERLOAD_CTRL_REJECT | The proxy is overloaded | N | The number of requests exceeds the processing capacity of proxy |
| -12045 | SVR_ERR_FAIL_TO_GET_CURSOR | The svr failed to obtain the traversal cursor, which may be caused by too many traversal requests at the same time, which are rarely encountered | N | |
| -12049 | PROXY_ERR_SQL_QUERY_MGR_IS_NULL | SQL query manager creation failed | N | It is generally caused by insufficient memory or unsuccessful ES service connection |
| -12051 | API_ERR_TABLE_NAME_MISSING | The restproxy request is not set the table name | N | Check the restproxy request parameters |
| -12301 | SVR_ERR_FAIL_OUT_OF_USER_DEF_RANGE | The value is outside the user-defined range | N | When the project team increases or decreases the value of a field (integer or floating point), such as the increase operation, the increased or decreased value exceeds or is lower than the user-defined range; For example, the access of user-defined field A is [10, 20], and the current value of field A is 15. If the request requests to increase this field's value by 6, the increased value will exceed 20, and this error will be returned; Or if the request requests to decrease this field's value by 6, the decreased value will be less than 10, and this error will be returned; |
| -12305 | PROXY_ERR_SQL_QUERY_INVALID_SQL_TYPE | Invalid sql request | N | SQL is illegal, or the type of SQL query is not supported by the back-end |
| -12307 | API_ERR_SOCKET_SEND_BUFF_IS_FULL | The api send buffer is full | Y | 1. Users send data packages too fast, and the number of packets is too large; 2. Check whether the network has reached the bottleneck, and the package sending is too slow; 3. Check that the number of back-end proxies is too small and packet receiving is too slow to reach the bottleneck |
| -12557 | SVR_ERR_INVALID_ARGUMENTS | Internal parameter error | N | |
| -12561 | PROXY_ERR_GET_TRANSACTION_FAILED | Transaction allocation failed. Please contact the administrator to increase the configuration of transaction concurrency | N | It is usually caused by the release of the transaction timeout, but the back-end message cannot find the corresponding transaction |
| -12563 | API_ERR_INVALID_MAGIC | The magic is incorrect, usually because of communication problems. If this problem occurs continuously, contact the administrator | N | The protocol's magic is incorrect, and the code should be followed. |
| -12817 | PROXY_ERR_ADD_TRANSACTION_FAILED | Transaction allocation failed. Please contact the administrator to increase the configuration of transaction concurrency | N | The transaction is pre-allocated. In swift, if the usage exceeds the configured value, this error will be reported |
| -12819 | API_ERR_TABLE_IS_NOT_EXIST | The table to be operated does not exist | Y | Generally, this error occurs when registering the table. Check whether the table on the page has been added successfully. It may be in the approval status. Please contact dba for approval |
| -13073 | PROXY_ERR_QUERY_FROM_INDEX_SERVER_FAILED | Global index querying failed | N | Global index is not configured. Please use it after configuration |
| -13075 | API_ERR_SHORT_BUFF | The restapi limits the request response body to 10 M; At present, http requests limit the size of the entire package to 10 M | N | Please check the restproxy request size |
| -13329 | PROXY_ERR_QUERY_FROM_INDEX_SERVER_TIMEOUT | Query global index timeout | N | The tcaplus service back-end does not return a response within a specified period of time. The error may be caused by service overload, network failure, or service disabled |
| -13331 | API_ERR_FLOW_CONTROL | api_flow_control | N | |
| -13585 | PROXY_ERR_QUERY_FOR_CONVERT_TCAPLUS( )_REQ_TO_INDEX_SERVER_REQ_FAILED | Failed to parse sql statement of global index | N | In general, the SQL statement on the user request side is invalid, resulting in parsing failure at the back end |
| -13587 | API_ERR_COMPRESS_SWITCH_NOT_SUPPORTED( )_REGARDING_THIS_CMD | The protocol compression SetCompressSwitch called for a command that does not support protocol compression | N | The currently supported command words for setting protocol compression are: TCAPLUS_CMD_GET_REQ, TCAPLUS_CMD_BATCH_GET_REQ, TCAPLUS_CMD_GET_DURING_MOVE_REQ |
| -13837 | SVR_ERR_INVALID_SELECT_ID_FOR_UNION | Internal error, please contact the administrator | N | |
| -13841 | PROXY_ERR_QUERY_INDEX_FIELD_NOT_EXIST | Index field does not exist | N | The field specified in the query statement in SQL is not found in the table definition of tcaplus. Confirm whether the fields of the client are defined in tcaplus |
| -13843 | API_ERR_FAILED_TO_FIND_ROUTE | The background network is abnormal, and the request cannot be sent successfully. If this error persists, please contact the administrator | Y | The route cannot be found, gameserver cannot find an available tcaproxy and it needs to follow up on the log. |
| -14093 | SVR_ERR_CAN_NOT_FIND_SELECT_ENTRY_FOR_UNION | Internal error, please contact the administrator | N | |
| -14097 | PROXY_ERR_THIS_SQL_IS_NOT_SUPPORT | Unsupported SQL | N | The proxy does not support the current SQL type |
| -14099 | API_ERR_OVER_MAX_PKG_SIZE | The single record to be operated exceeds 10 M after packaging | Y | There is a limit to the size of the record, so it is necessary to reduce the size of the record; Confirm the size limit of a single record according to the version. 10 M is supported after version 3.40.0, and 1 M is supported in the previous versions |
| -14353 | PROXY_ERR_NO_SUCH_APPID | Proxy authentication failed. The service authentication information was not found | N | |
| -14609 | PROXY_ERR_NO_APP_USER_PASSWD | The proxy cannot find the user authentication information | N | |
| -14865 | PROXY_ERR_NO_APP_USER_PASSWD_RECORD | The proxy cannot find the user authentication information | N | |
| -15117 | SVR_ERR_INVALID_ARRAY_COUNT | Invalid array size | Y | Check TDR rules |
| -15121 | PROXY_ERR_NO_APP_USER_OPT | The proxy cannot find the user authentication information | N | |
| -15123 | API_ERR_ADD_RECORD | failed to add a new record into request | N | |
| -15373 | SVR_ERR_REJECT_REQUEST_BECAUSE_ROUTE( )_IN_REJECT_STATUS | Reject the request. It may be caused by the routing error when the svr is in the relocation state. | N | |
| -15377 | PROXY_ERR_NO_APP_USER_OPT_RECORD | The proxy cannot find the user authentication information | N | The tcaplus proxy does not cache user password information of the specified app, which often occurs in internal system logic errors |
| -15379 | API_ERR_ZONE_IS_NOT_EXIST | The zone id to be operated does not exist | N | Check whether the zone exists in the app on the page Whether the environment of tcaplus is connected correctly |
| -15635 | API_ERR_TRAVERSER_IS_NOT_EXIST | When the packet is received, the traverser has been destroyed or stopped. This error is generally not returned to the user and can be ignored | N | |
| -15885 | SVR_ERR_FAIL_INVALID_FIELD_VALUE | Invalid field value | N | |
| -16141 | SVR_ERR_FAIL_PROTOBUF_FIELD_GET | The PB table's GetRecord operation failed. Please contact the administrator | Y | |
| -16147 | API_ERR_INSTANCE_INIT_LOG_FAILURE | Failed to initialize the log module | N | |
| -16389 | TXHDB_ERR_INVALID_VALUE_DATABLOCK_NUM | The number of proxy value datablocks is abnormal. Please contact the administrator | N | |
| -16403 | API_ERR_CONNECTOR_IS_ABNORMAL | The connection is abnormal | N | |
| -16653 | SVR_ERR_FAIL_PROTOBUF_FIELD_UPDATE | PB table's FieldSetRecord operation failed, please contact the administrator | Y | Check whether the operation field already exists on the server |
| -16659 | API_ERR_WAIT_RSP_TIMEOUT | Used by sqldriver, waiting for response timeout | N | It rarely occurs. Please contact tcaplus for troubleshooting |
| -16901 | TXHDB_ERR_COMPRESSION_FAIL | Compression failed | N | |
| -16909 | SVR_ERR_FAIL_PROTOBUF_FIELD_INCREASE | PB table's FieldIncRecord operation failed, please contact the administrator | Y | |
| -16915 | API_ERR_CONVERT_DIR_DOMAIN | The api failed to convert the dir domain | Y | Ping the dir domain and try to convert it. Possible reasons include: 1. The domain name is incorrect or does not exist. 2. The DNS configuration of the client is incorrect. 3. Confirm whether the dir address is filled correctly, such as missing “tcp://xxx:9999” |
| -17157 | TXHDB_ERR_DECOMPRESSION_FAIL | Failed to decompress | N | |
| -17165 | SVR_ERR_FAIL_PROTOBUF_FIELD_TAG_MISMATCH | The PB table tag does not match | Y | The project team confirms whether the definition of the gameserver-side table is consistent with that of the Tcaplus table |
| -17171 | API_ERR_NET_THREAD_START_TIMEOUT | The api failed to wait for the network thread to start | N | 1. Generally, the CPU is stuck, resulting in a slow sub-thread startup; 2. The network thread failed to copy the log handle of the main thread, resulting in a startup failure; This is usually caused by the clone failure of tlog; If it is Fin before Init, it is recommended to destroy the log handle after Fini and regenerate it |
| -17427 | API_ERR_DIR_CONNECT_FAILED | Dir conncetion failed | Y | Check network problems and try to telnet the dir |
| -17683 | API_ERR_DIR_SIGNUP_FAILED | Dir authentication failed | Y | Check the password |
| -17938 | API_ERR_DIR_GET_PROXYLIST_TIMEOUT | Get a proxy list from the directory timeout | N | Check the dir module to find the reason for the slow list return |
| -18195 | API_ERR_PROXY_CONNECT_FAILED | The connection from API to proxy failed | Y | 1. Confirm whether it is a network limitation, whether the strategy from dev to idc is enabled, and whether the proxy is enabled again after relocation; 2. Telnet the network port of the proxy to see whether it can be connected; 3. Curl the network port of the proxy to see whether there are any permission errors; 4. Since the number of proxy connections is limited to 3000, contact tcaplus to check whether there are too many clients |
| -18451 | API_ERR_COMPARE_TABLE_META_FAILED | Meta comparison between the api and svr failed | Y | Check whether the local and oms tables are consistent |
| -18701 | SVR_ERR_FAIL_PARTKEY_INSERT_NOT_SUPPORT | InsertByPartkey is not supported | N | |
| -18957 | SVR_ERR_FAIL_SQL_FILTER_FAILED | Failed to execute sql filtering in the distributed index | N | |
| -33541 | TXHDB_ERR_ADD_LSIZE_EXCEEDS( )_MAX_TSD_VALUE_BUFF_SIZE | Internal error, please contact the administrator | N | |
| -34053 | TXHDB_ERR_TOO_BIG_KEY_BIZ_SIZE | The key exceeds the maximum limit of 1 KB | N | |
| -34309 | TXHDB_ERR_TOO_BIG_VALUE_BIZ_SIZE | The value exceeds the maximum limit of 10 MB | N | |
| -34565 | TXHDB_ERR_INDEX_NO_EXIST | The index does not exist | N | |
| -39685 | TXHDB_ERR_FILE_EXCEEDS_LSIZE_LIMIT | A single data shard exceeds the maximum limit of 256 GB, resulting in write failure | Y | When this problem occurs, expand the capacity |
| -3089 | PROXY_ERR_ROUTE_MSG | The proxy cannot find the route | Y | 1.Check whether the table is added. If yes, please contact Tcaplus 2.On the business side, when getting the key and value, if the key buffer is empty, the key cannot be found, resulting in a routing error. If it is not the above situation, please contact Tcaplus to check if the proxy is online and to review the relevant logs. |
| -1280 | GEN_ERR_ECMGR_DUPLICATED_ERROR_CODE | Error code table initialization failed. Duplicate error codes are defined | N | The TcapErrCodeInit function is not safe to be called in multiple threads, which may cause failure. Put TcapErrCodeInit into the main thread for initialization, or add a synchronization lock |
| -1297 | TCAPROXY_ERROR_SYSTEM_ERROR | PROXY Error | N | It is possible that the transaction or action resources of the proxy have been exhausted (please contact tcaplus helper to confirm through the proxy log), and further confirmation can be made through the proxy log |
| 269 | SVR_ERR_FULL_SORTLIST_CANT_INSERT | The newly inserted data in the sortlist table exceeds the maximum number of list elements, resulting in insertion failure | N | The newly inserted data in the sortlist table exceeds the maximum number of list elements, and even if inserted, it will be immediately eliminated. The insertion fails and this error code is returned |