Skip to main content
Version: 3.13

ScalarDB Cluster Error Codes

This page provides a list of error codes in ScalarDB Cluster.

Error code classes and descriptions​

ClassDescription
CLUSTER-1xxxxErrors for the user error category.
CLUSTER-2xxxxErrors for the concurrency error category
CLUSTER-3xxxxErrors for the internal error category

CLUSTER-1xxxx status codes​

CLUSTER-10000​

Message

The namespace does not exist. Namespace: %s

CLUSTER-10001​

Message

The table does not exist. Table: %s

CLUSTER-10002​

Message

The user does not exist. User: %s

CLUSTER-10003​

Message

ClusterConfig is not specified

CLUSTER-10004​

Message

The get type is unspecified

CLUSTER-10005​

Message

The get type is unrecognized

CLUSTER-10006​

Message

The value of the column is not set. Column: %s

CLUSTER-10007​

Message

The scan type is unspecified

CLUSTER-10008​

Message

The scan type is unrecognized

CLUSTER-10009​

Message

The order is unspecified

CLUSTER-10010​

Message

The order is unrecognized

CLUSTER-10011​

Message

The clustering order is unspecified

CLUSTER-10012​

Message

The clustering order is unrecognized

CLUSTER-10013​

Message

The put condition type is unspecified

CLUSTER-10014​

Message

The put condition type is unrecognized

CLUSTER-10015​

Message

The delete condition type is unspecified

CLUSTER-10016​

Message

The delete condition type is unrecognized

CLUSTER-10017​

Message

The operator is unspecified

CLUSTER-10018​

Message

The operator is unrecognized

CLUSTER-10019​

Message

The mutation is not set

CLUSTER-10020​

Message

The data type is unspecified

CLUSTER-10021​

Message

The data type is unrecognized

CLUSTER-10022​

Message

The user option is unspecified

CLUSTER-10023​

Message

The user option is unrecognized

CLUSTER-10024​

Message

The privilege is unspecified

CLUSTER-10025​

Message

The privilege is unrecognized

CLUSTER-10026​

Message

The username is not set

CLUSTER-10027​

Message

This feature is not supported in ScalarDB Cluster

CLUSTER-10028​

Message

The property 'scalar.db.contact_points' must not be empty

CLUSTER-10029​

Message

The property 'scalar.db.contact_points' must be prefixed with 'indirect:' or 'direct-kubernetes:'

CLUSTER-10030​

Message

The format of the property 'scalar.db.contact_points' for direct-kubernetes client mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'

CLUSTER-10031​

Message

The property 'scalar.db.sql.cluster_mode.contact_points' must not be empty

CLUSTER-10032​

Message

The property 'scalar.db.sql.cluster_mode.contact_points' must be prefixed with 'indirect:' or 'direct-kubernetes:'

CLUSTER-10033​

Message

The format of the property 'scalar.db.sql.cluster_mode.contact_points' for direct-kubernetes client mode is 'direct-kubernetes:<NAMESPACE_NAME>/<ENDPOINT_NAME>' or 'direct-kubernetes:<ENDPOINT_NAME>'

CLUSTER-2xxxx status codes​

CLUSTER-20000​

Message

The hop limit is exceeded

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

CLUSTER-3xxxx status codes​

CLUSTER-30000​

Message

Getting local IP addresses failed

CLUSTER-30001​

Message

Getting a cluster node object from the cache failed. Cluster Node IP Address: %s

CLUSTER-30002​

Message

The ring is empty

CLUSTER-30003​

Message

Getting the Kubernetes API client failed

CLUSTER-30004​

Message

Reading the Kubernetes endpoint failed. Namespace: %s; Name: %s; Code: %d; Response Headers: %s; Response Body: %s

CLUSTER-30005​

Message

Configuring TLS failed