ScalarDB Cluster Error Codes
This page provides a list of error codes in ScalarDB Cluster.
Error code classes and descriptions​
| Class | Description |
|---|---|
DB-CLUSTER-1xxxx | Errors for the user error category |
DB-CLUSTER-2xxxx | Errors for the concurrency error category |
DB-CLUSTER-3xxxx | Errors for the internal error category |
DB-CLUSTER-1xxxx status codes​
The following are status codes and messages for the user error category.
DB-CLUSTER-10000​
Message
The namespace does not exist. Namespace: %s
DB-CLUSTER-10001​
Message
The table does not exist. Table: %s
DB-CLUSTER-10002​
Message
The user does not exist. User: %s
DB-CLUSTER-10004​
Message
The get type is unspecified
DB-CLUSTER-10005​
Message
The get type is unrecognized
DB-CLUSTER-10006​
Message
The value of the column is not set. Column: %s
DB-CLUSTER-10007​
Message
The scan type is unspecified
DB-CLUSTER-10008​
Message
The scan type is unrecognized
DB-CLUSTER-10009​
Message
The order is unspecified
DB-CLUSTER-10010​
Message
The order is unrecognized
DB-CLUSTER-10011​
Message
The clustering order is unspecified
DB-CLUSTER-10012​
Message
The clustering order is unrecognized
DB-CLUSTER-10013​
Message
The put condition type is unspecified
DB-CLUSTER-10014​
Message
The put condition type is unrecognized
DB-CLUSTER-10015​
Message
The delete condition type is unspecified
DB-CLUSTER-10016​
Message
The delete condition type is unrecognized
DB-CLUSTER-10017​
Message
The operator is unspecified
DB-CLUSTER-10018​
Message
The operator is unrecognized
DB-CLUSTER-10019​
Message
The mutation is not set
DB-CLUSTER-10020​
Message
The data type is unspecified
DB-CLUSTER-10021​
Message
The data type is unrecognized
DB-CLUSTER-10022​
Message
The user option is unspecified
DB-CLUSTER-10023​
Message
The user option is unrecognized
DB-CLUSTER-10024​
Message
The privilege is unspecified
DB-CLUSTER-10025​
Message
The privilege is unrecognized
DB-CLUSTER-10026​
Message
The username is not set
DB-CLUSTER-10027​
Message
This feature is not supported in ScalarDB Cluster
DB-CLUSTER-10028​
Message
The contact points must not be empty. Property: %s
DB-CLUSTER-10029​
Message
The contact points must be prefixed with 'indirect:' or 'direct-kubernetes:'. Property: %s
DB-CLUSTER-10030​
Message
The format of the contact points for the direct-kubernetes mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'. Property: %s
DB-CLUSTER-10035​
Message
The update condition type is unspecified
DB-CLUSTER-10036​
Message
The update condition type is unrecognized
DB-CLUSTER-10037​
Message
The two-phase commit interface is not supported
DB-CLUSTER-10039 ​
Message
The policy state is unspecified
DB-CLUSTER-10040​
Message
The policy state is unrecognized
DB-CLUSTER-10041​
Message
The access mode is unspecified
DB-CLUSTER-10042​
Message
The access mode is unrecognized
DB-CLUSTER-10043​
Message
The service does not exist. Service Class: %s
DB-CLUSTER-10044​
Message
The policy does not exist. Policy: %s
DB-CLUSTER-10057​
Message
The operation is not set
DB-CLUSTER-10058​
Message
The batch result is not set
DB-CLUSTER-10059​
Message
Resuming a transaction is not allowed when piggyback-begin is enabled
DB-CLUSTER-10060​
Message
Resuming a transaction is not allowed when write-buffering is enabled
DB-CLUSTER-10061​
Message
The transaction has not begun yet. This situation may occur when piggyback-begin is enabled
DB-CLUSTER-10062​
Message
The transaction already exists. Transaction ID: %s
DB-CLUSTER-10063​
Message
The authentication method is unspecified
DB-CLUSTER-10064​
Message
The authentication method is unrecognized
DB-CLUSTER-10065​
Message
Nested holder calls are not supported
DB-CLUSTER-10066​
Message
No value set in the thread-local holder. Use the holder's execute method to set it.
DB-CLUSTER-10067​
Message
The auth type specified in attributes is invalid. Auth type: %s
DB-CLUSTER-10068​
Message
The required attribute is missing. Auth type: %s; Attribute: %s
DB-CLUSTER-10069​
Message
The write type is unspecified
DB-CLUSTER-10070​
Message
The write type is unrecognized
DB-CLUSTER-10071​
Message
The write-set detail level is unspecified
DB-CLUSTER-10072​
Message
The write-set detail level is unrecognized
DB-CLUSTER-10073​
Message
The transaction ID is required for this operation but was not specified
DB-CLUSTER-10074​
Message
'scalar.db.cluster.id' must be configured when 'scalar.db.cluster.node.transaction_participant.enabled' is enabled
DB-CLUSTER-10075​
Message
The cluster is not configured. Cluster ID: %s; Configured clusters: %s
DB-CLUSTER-10076​
Message
'scalar.db.cluster.transaction_coordinator.clusters' must be configured with at least one cluster ID
DB-CLUSTER-10077​
Message
The cluster IDs in 'scalar.db.cluster.transaction_coordinator.clusters' must be unique. Duplicate cluster ID: %s
DB-CLUSTER-10078​
Message
Joining a transaction is not allowed when piggyback-begin is enabled
DB-CLUSTER-10079​
Message
Joining a transaction is not allowed when write-buffering is enabled
DB-CLUSTER-10080​
Message
'scalar.db.cluster.id' must be configured for the cluster connection when 'scalar.db.cluster.client.transaction_coordinator.enabled' is enabled
DB-CLUSTER-10081​
Message
The cluster connection is not configured, so this operation is not available. A transaction coordinator client without a cluster connection can only begin, commit, and roll back transactions
DB-CLUSTER-10082​
Message
Joining a transaction is not allowed when authentication is enabled
DB-CLUSTER-10083​
Message
Resuming a transaction is not allowed when authentication is enabled
DB-CLUSTER-2xxxx status codes​
The following are status codes and messages for the concurrency error category.
DB-CLUSTER-20000​
Message
The hop limit is exceeded
DB-CLUSTER-20001​
Message
A transaction associated with the specified transaction ID is not found. The transaction might have expired, or the cluster node that handled the transaction might have been restarted. Transaction ID: %s
DB-CLUSTER-20002​
Message
A scanner associated with the specified scanner ID is not found. The scanner might have expired, or the cluster node that handled the scanner might have been restarted. Transaction ID: %s; Scanner ID: %s
DB-CLUSTER-20003​
Message
The transaction was aborted because its authentication token was rejected during commit. The token snapshot of an in-flight transaction cannot be refreshed, so retry the transaction from the beginning
DB-CLUSTER-3xxxx status codes​
The following are status codes and messages for the internal error category.
DB-CLUSTER-30000​
Message
Getting local IP addresses failed
DB-CLUSTER-30001​
Message
Getting a cluster node object from the cache failed. Cluster Node IP Address: %s
DB-CLUSTER-30002​
Message
The ring is empty
DB-CLUSTER-30003​
Message
Getting the Kubernetes API client failed
DB-CLUSTER-30004​
Message
Reading the Kubernetes endpoint failed. Namespace: %s; Name: %s; Code: %d; Response Headers: %s; Response Body: %s
DB-CLUSTER-30005​
Message
Configuring TLS failed
DB-CLUSTER-30006​
Message
No nearest cluster nodes are found