Errors and Solutions

IGN-AUTHENTICATION-1

Authentication error caused by unsupported authentication type.

Check the client configuration and use the supported configuration type.

IGN-AUTHENTICATION-2

Authentication error caused by invalid credentials.

Check and correct user credentials.

IGN-AUTHENTICATION-3

Basic authentication provider is not found.

Configure basic authentication provider.

GG-CACHE-1

This error occurs when a transaction includes both a cache and a table, or multiple caches with different CacheWriteMode types.

Review your transaction configuration to ensure you’re only combining tables or caches with the same CacheWriteMode within a single transaction.

GG-CACHESTORE-1

Cache store configuration failure.

Check the exception message for information on why the error occurred.

GG-CACHESTORE-2

Cache store access error.

Check the exception message for information on why the error occurred.

IGN-CATALOG-1

Command to the catalog has not passed the validation.

See the exception message for details. Typically, this is either caused by incorrect DDL query (same as IGN-SQL-4) or an internal GridGain 9 error.

IGN-CDC-1

General CDC error.

Check the exception message for details. Review CDC configuration and logs. Verify source and sink availability. Retry the operation after resolving the underlying issue.

IGN-CDC-2

Internal CDC error indicating that there is a bug in the CDC codebase.

This is an unexpected internal error. Collect full logs and stack traces. Report the issue to GridGain support with reproduction steps. Restart the affected CDC components.

IGN-CDC-3

CDC validation error.

Check the exception message for validation details. Verify CDC configuration syntax and parameters. Ensure that the source and sink definitions are correct. Correct the configuration and retry.

IGN-CDC-4

CDC sink initialization error.

Check CDC sink configuration. Verify that the sink endpoint is accessible. Ensure that sink credentials and permissions are correct. Check cluster logs for resource constraints. Retry sink initialization.

IGN-CDC-5

CDC replication start error.

Verify that both the source and sink are properly configured. Confirm network connectivity between replication nodes. Ensure replication prerequisites are met. Check logs for specific failure reasons. Retry replication startup.

IGN-CDC-6

CDC replication stop error.

Check node status and cluster connectivity. Verify that the replication group is accessible. Review logs for termination issues. Force-stop replication if necessary and retry.

IGN-CDC-7

CDC sink already exists.

Use a different sink name when creating a new sink, or drop the existing sink before creating a new one with the same name. Verify sink naming conventions.

IGN-CDC-8

CDC source already exists.

Use a different source name when creating a new source, or drop the existing source before creating a new one with the same name. Verify source naming conventions.

IGN-CDC-9

CDC source not found.

Verify that the source name is correct. Check that the source has been created. List available sources to confirm its presence. Create the source if necessary.

IGN-CDC-10

CDC sink not found.

Verify that the sink name is correct. Check that the sink has been created. List available sinks to confirm its presence. Create the sink if necessary.

IGN-CDC-11

CDC replication not found.

Verify that the replication ID or name is correct. Check that replication has been configured. List active replications to confirm its presence. Configure replication if necessary.

IGN-CDC-12

CDC replication already exists.

Use a different replication ID or name, or drop the existing replication before creating a new one with the same identifier. Verify replication naming conventions.

IGN-CDC-13

CDC is disabled.

Enable CDC in the cluster configuration. Update node configuration to enable CDC. Restart nodes with CDC enabled. Verify that CDC is enabled at both the cluster and node levels.

IGN-CLIENT-1

Connection to client failed. This error is usually caused by incorrect address or connection timeout.

Check the exception message. If a timeout occurred, make sure the timeout values in client and server configurations allow for long-running requests.

IGN-CLIENT-2

An issue occurred with connection protocol. This error can be caused by using an incompatible client version or data corruption.

Check the exception message. If data corruption occurred, recover the data. If client versions are not compatible, use the correct client version.

IGN-CLIENT-3

Protocol version does not support a specific feature. Typically this is caused by version mismatch between client and server.

Update the client or the server to a newer version or do not use incompatible features.

IGN-CLIENT-4

Failed to find the table by ID.

Check if the table ID is correct.

IGN-CLIENT-5

An error occurred with client configuration.

Check the exception message for more information and fix the client configuration.

IGN-CLIENT-6

Cluster ID mismatch. This error can be caused by the client connecting to multiple different clusters.

Check client configuration to make sure all endpoints belong to the same cluster.

IGN-CLIENT-7

Client SSL configuration is not valid.

Check the exception message for more information. Make sure SSL configuration matches server-side configuration.

IGN-CLIENT-8

Client handshake message error. This is usually caused by the client trying to connect to a wrong endpoint (for example, REST) or a non-GridGain 9 process is trying to connect to a GridGain 9 endpoint.

Check the exception message for more information. If the issue is with client, check and fix client configuration. If a third-party client is trying to connect, check what it is and fix the configuration.

IGN-CLIENT-9

Server to client request failed.

Check the network connectivity, client availability, and server logs for errors.

IGN-CODEDEPLOY-1

Access attempt to a non-existing deployment unit.

Make sure the deployment unit is specified correctly.

IGN-CODEDEPLOY-2

Duplicate deployment unit.

Make sure deployment unit is unique. Update deployment unit name or version.

IGN-CODEDEPLOY-3

Deployment unit content read error.

Check the error message for details.

IGN-CODEDEPLOY-4

Deployment unit is unavailable for computing.

Check the error message for details.

IGN-CODEDEPLOY-5

Deployment unit zip deploy error.

Verify the deployment package is not corrupted and retry deployment.

IGN-CODEDEPLOY-6

Deployment unit write to fs error.

Check file system permissions and available disk space.

IGN-COMMONCFG-1

Configuration apply failed.

Check the config for errors and ensure the path to the config file is correct.

IGN-COMMONCFG-2

Configuration parse error.

Check cluster logs for syntax errors in the config file.

IGN-COMMONCFG-3

Configuration validation error.

Correct invalid or inconsistent configuration parameters and retry startup.

IGN-CMN-1

Operation was stopped because node is stopping.

Check that the cluster is up and running and try again.

IGN-CMN-2

Operation was stopped because the component is not started.

Wait for the node to complete the startup process and start all components.

IGN-CMN-3

Operation failed because an illegal argument or argument in a wrong format has been passed.

Check the exception message for additional information. Specific actions depend on the operation that triggered the error.

IGN-CMN-4

Operation failed because SSL could not be configured.

Check the exception message for more information and update the configuration.

IGN-CMN-5

Operation failed because a node has left the cluster.

Wait for the node to return to the cluster, or use a different node.

IGN-CMN-6

Operation failed because the cursor is already closed.

Check the exception message to find out why the cursor was closed before the operation.

IGN-CMN-7

An error occurred while closing resources.

Check the exception message to find out why the resource was closed before the operation.

IGN-CMN-8

An error occurred while marshalling or unmarshalling objects.

Check object serialization logic and ensure all involved classes are compatible.

IGN-CMN-9

The method cannot return a null value.

Verify the method’s implementation and ensure it returns a valid non-null result.

IGN-CMN-65535

Internal error has occurred.

This an unexpected internal error in GridGain 9. In most cases, receiving it indicates a bug.

IGN-COMPUTE-1

Classpath error.

Check the exception message for additional information and fix the classpath error.

IGN-COMPUTE-2

Class loader error.

Most likely, this is caused by an internal error in GridGain 9.

IGN-COMPUTE-3

Failed to initialize the job class.

Check the exception message for more information.

IGN-COMPUTE-4

Execution queue overflow.

Increase the compute.queueMaxSize configuration parameter to allow for larger queue.

IGN-COMPUTE-5

Compute job status transition error.

Retry the operation or check job status.

IGN-COMPUTE-6

Failed to cancel compute job.

Check the error message and fix the issue in it.

IGN-COMPUTE-7

Compute job result not found.

Make sure the specified job ID exists.

IGN-COMPUTE-8

Compute job state cannot be retrieved.

Make sure the specified job ID exists. If it does, check the node logs for additional information.

IGN-COMPUTE-9

Compute job failed.

Check the exception message for more information on the reason for failure.

IGN-COMPUTE-10

Failed to resolve primary replica for colocated execution.

Check the exception message for additional information.

IGN-COMPUTE-11

Failed to change job priority.

Check the exception message for additional information.

IGN-COMPUTE-12

Specified node is not found in the cluster.

Make sure the specified node ID is correct and the node with the ID is in the cluster.

IGN-COMPUTE-13

Incompatible types for argument or result in compute job.

Make sure that defined compute job argument and result marshallers match on both server and client sides.

IGN-COMPUTE-14

Compute job cancelled.

Run the job again.

IGN-COMPUTE-15

Platform compute executor error.

Check executor logs for the issue.

IGN-CONTINUOUSQUERY-1

Watermark represents a timestamp older than the data available in the table.

Use a more recent watermark timestamp. Increase data retention period with ignite.gc.lowWatermark.dataAvailabilityTimeMillis. Make sure that continuous query subscriber keeps up with the updates.

IGN-CONTINUOUSQUERY-2

Table was dropped and historical data is no longer available.

Increase data retention period with ignite.gc.lowWatermark.dataAvailabilityTimeMillis. Make sure that continuous query subscriber keeps up with the updates.

IGN-WORKERS-1

System worker does not update its heartbeat for a long time. Typically, this means that the node has stalled or is running slowly.

Restart the node.

IGN-WORKERS-2

System-critical operation timed out.

Restart the node.

GG-DCR-1

Generic DCR error.

Check the exception message for information on why the error occurred.

GG-DCR-2

Failed to create replication.

Check the exception message for information on why the error occurred.

GG-DCR-3

Failed to start replication.

Check the exception message for information on why the error occurred.

GG-DCR-4

Replication cannot be removed because it is still running.

Stop the replication and try again.

GG-DCR-5

The source and target schemas for the replicated tables are incompatible.

Make sure the local and remote clusters have the same schema.

GG-DCR-6

Replication failed to stop.

Check the exception message for information on why the error occurred.

GG-DCR-7

Replicated source table doesn’t exist.

Check the table name used in replication and create the table if necessary.

GG-DCR-8

Replication failed to start second replication for the same table.

Check what replication is already using the table and stop it if needed.

GG-DCR-9

Replication with the specified name is not found.

Check the replication name and try again.

GG-DCR-10

Replication with the specified name already exists.

Use a different name for the new replication.

GG-DCR-11

There is no specified table on the source cluster.

Check the source table name.

GG-DCR-12

Replication to self is not allowed.

Remove the local cluster endpoint from the replication target configuration and use a different remote cluster.

IGN-DISTRZONES-1

Distribution zone is not found.

Check the distribution zone name used. Most likely, it is incorrect.

IGN-DISTRZONES-2

Empty data nodes.

Add data nodes to the distribution zone.

IGN-RECOVERY-1

Partition ID is not in valid range.

Check the exception message. Most likely, the specified partition ID is not correct.

IGN-RECOVERY-2

Nodes were not found.

Check the exception message. Most likely, the specified node ID is not correct.

IGN-RECOVERY-3

Failed to recover partition states.

Retry the operation. If it fails again, check the exception message for more information.

IGN-RECOVERY-4

Cluster is under load.

Retry the operation when the cluster has less load.

IGN-RECOVERY-5

Error when not enough alive nodes to perform restart with clean up.

Start additional nodes or restore failed ones before retrying recovery.

IGN-RECOVERY-6

Error when node names are not in valid set.

Check cluster configuration and correct invalid node names.

IGN-EMBEDDED-1

Cluster is not yet initialized.

Initialize the cluster before performing operations.

IGN-EMBEDDED-2

Cluster initialization failed.

Check initialization logs and fix configuration or resource issues.

IGN-EMBEDDED-3

Node not started.

Start the node before performing operations.

IGN-EMBEDDED-4

Node start failed.

Check startup logs and configuration for errors, then retry startup.

GG-ENCRYPTION-1

Missing key provider to decrypt data from storage.

Specify the key provider.

GG-ENCRYPTION-2

Key provider configuration is not valid.

Check the key provider configuration and update it.

GG-ENCRYPTION-3

Failed to initialize encryption provider.

Check the exception message for information on why the error occurred.

GG-ENCRYPTION-4

Missing data encryption key to decrypt data from storage.

Make sure the storage you are using contains the required encryption key.

GG-ENCRYPTION-5

AWS KMS common error.

Check the exception message for details. Verify AWS KMS configuration and permissions.

GG-ENCRYPTION-6

AWS KMS key not found error.

Verify that the specified AWS KMS key exists and is accessible.

GG-ENCRYPTION-7

AWS KMS key found but disabled, so cannot be used.

Enable the AWS KMS key or use a different key.

IGN-GC-14

Garbage collector closed error.

Restart the node to reinitialize the garbage collector.

IGN-IDX-1

Failed to find the specified index.

Make sure the index exists.

IGN-IDX-2

Specified index already exists.

Make sure the index does not exist when creating it.

GG-JWT-1

JWT validation error.

Check the exception message for information on why the error occurred.

GG-JWT-2

JWT serialization or deserialization error.

Check the exception message for information on why the error occurred.

GG-LDAP-1

General LDAP error.

Check the exception message for information on why the error occurred.

GG-LDAP-2

LDAP client initialization failed.

Check the exception message for information on why the initialization failed.

GG-LDAP-3

LDAP search request failed.

Check the exception message for information on why the request failed.

GG-LDAP-4

LDAP user not found.

Check if username is correct and make sure that the user exists.

GG-LICENSE-1

Generic license error.

Check the exception message for information on why the error occurred.

GG-LICENSE-2

A license is missing for cluster.

Make sure to add the license when initializing the cluster.

GG-LICENSE-3

A license has been modified.

Contact GridGain support.

GG-LICENSE-4

A license does not contain the required features.

Contact GridGain support.

GG-LICENSE-5

Blocked licenses list has been modified.

Contact GridGain support.

IGN-MARSHALLING-1

Marshalling error.

Check serialization logic and class compatibility.

IGN-MARSHALLING-2

Unsupported object type error.

Use only supported object types for serialization.

IGN-MARSHALLING-3

Unmarshalling error.

Verify data format and class versions match between nodes.

IGN-META-1

Failed to start the underlying key value storage.

Check storage configuration and ensure the storage path is accessible.

IGN-META-2

Failed to restore the underlying key value storage.

Verify backup integrity and retry restoration.

IGN-META-3

Failed to compact the underlying key value storage.

Check storage health and retry compaction.

IGN-META-4

Failed to perform an operation on the underlying key value storage.

Check storage logs and system resources, then retry the operation.

IGN-META-5

Failed to perform an operation within a specified time period.

Check storage logs and system resources, then retry the operation.

IGN-META-6

Failed to perform a read operation on the underlying key value storage because the revision has already been compacted.

Retry the read with a newer revision.

IGN-META-7

Failed to start a node because metastorage has diverged as a result of MG recovery.

Clear the node of data and add it to the cluster as a blank node.

IGN-NETWORK-1

The node with the specified ID is not in the physical topology.

Check the error message and node ID. Update node ID if it is incorrect. If the node is offline, check why and bring it back online.

IGN-NETWORK-2

Port is already in use.

Most likely, GridGain 9 tried to access the port occupied by a different process. Change the port or free it, and then restart the node.

IGN-NETWORK-3

File transfer error.

Check network connectivity and retry the file transfer.

IGN-NETWORK-4

File validation error.

Ensure the file is not corrupted.

IGN-NETWORK-5

Recipient node has left the physical topology.

Check the error message. The node is unavailable and need to be brought back into the cluster.

IGN-NETWORK-6

Could not resolve address. Most likely, the IP address specified in the operation is not available locally.

Change the node configuration to make the address available or use a different IP address.

IGN-NODECFG-1

Failed to read configuration.

Make sure that the node has access to the configuration file.

IGN-NODECFG-2

Failed to create a configuration file.

Check if the node has write permissions to the folder where configuration is.

IGN-NODECFG-3

Failed to write configuration.

Check if the node has write permissions to the folder where configuration is.

IGN-NODECFG-4

Failed to parse configuration.

Make sure the configuration file is correct.

IGN-NODECFG-5

Node was unable to pass the validation step.

Fix the invalid or mismatched configuration and retry joining the cluster.

GG-NODEKEYMGMT-1

Node key decoding error.

Check the exception message for information on why the error occurred.

GG-NODEKEYMGMT-2

Node key expired error.

Update the node key.

GG-NODEKEYMGMT-3

Node key generation error.

Check the exception message for information on why the error occurred and try again.

GG-NODEKEYMGMT-4

Node key store error.

Check the exception message for information on why the error occurred. Verify node key storage is accessible.

GG-NODEKEYMGMT-5

Node key serialization or deserialization error.

Check the exception message for information on why the error occurred.

GG-NODEKEYMGMT-6

Node key validation error.

Check the exception message for information on why the error occurred.

IGN-PLACEMENTDRIVER-1

Primary replica await timeout error.

Increase the timeout.

IGN-PLACEMENTDRIVER-2

Primary replica await error.

Check replica status and cluster connectivity.

IGN-PLACEMENTDRIVER-3

Error that occurs if there are no assignments for a group.

Ensure replicas are assigned to the group and assign if needed.

GG-PITR-1

Generic PITR error.

Check the exception message for information on why the error occurred.

GG-PITR-2

Error indicating that recovery has been canceled.

Check the exception message for information on what caused it to stop.

GG-RBAC-1

Generic access control error.

See the exception message for details. Typically, this error is caused either by the disabled security or by an unexpected issue.

GG-RBAC-2

User not found.

Check if username is correct and make sure that the user exists.

GG-RBAC-3

An issue occurred while validating the user.

Check the exception message for details.

GG-RBAC-4

User with the specified name already exists.

Check if username is correct, or use a different username.

GG-RBAC-5

An error occurred while updating user info.

Check the exception message for details and try again.

GG-RBAC-6

User assignment already exists.

Check the exception message for details and try again.

GG-RBAC-7

Role with the specified name was not found

Check if role name is correct, or create a role with required name.

GG-RBAC-8

Role with the specified name already exists.

Check if role name is correct, or use a different role name.

GG-RBAC-9

An issue occurred while validating role information

Check the exception message for details.

GG-RBAC-10

Failed to assign the role to the user.

Verify that both the user and the role exist.

GG-RBAC-11

Role assignment already exists.

The role with the specified name is already assigned to the user. No action is required.

GG-RBAC-12

The role already has the specified privilege.

The privilege is already added to the role. No action is required.

GG-RBAC-13

Failed to apply a privilege, as the privilege is invalid.

Check the privilege syntax. Typically, this is caused by trying to assign invalid action.

GG-RBAC-14

Failed to apply a privilege, as the action cannot have a selector, or the selector is not valid.

Remove a selector from the action, or correct the error in the selector.

GG-RBAC-15

User does not have permission to change access control permissions.

Rerun the operation with an authorized user.

GG-RBAC-16

An attempt to modify system user failed.

System user cannot be modified.

IGN-REP-1

Default error for the replication procedure.

Check the logs and take action depending on the cause.

IGN-REP-2

Replica with the same identifier already exists.

Replica start error. Check the logs for details.

IGN-REP-3

Replication timeout error.

Potential causes include prolonged replica startup, network issues, or node failures. Check the logs for error cause. Make sure that every partition group has a majority of nodes online.

IGN-REP-4

The replication level tried to handle an unsupported request.

Make sure there are no nodes having incompatible versions in the cluster.

IGN-REP-5

Replica is not ready to handle the request.

This can be caused by the replica unavailability or the primary replica absence. Check the logs for details related to the replica start issues. If the error is caused by the primary replica absence, make sure that partition groups are operational, check the logs for problems related to primary replica negotiation for the specific replication group.

IGN-REP-6

Replica is not the current primary replica.

This error indicates that the request was routed to a node that is not the current primary replica lease holder. Retry the operation, as it should automatically redirect to the correct lease holder. If primary replicas are changing frequently, verify that there are no node failures, network issues, or JVM/GC pauses causing primary replica expiration.

IGN-REP-7

Failed to close cursor.

General error, check the logs for details.

IGN-REP-8

Replica is already stopping.

Replica is being stopped, probably due to the node stop or rebalancing. No action is required unless this behavior is unexpected. Otherwise check the logs for details.

IGN-REP-9

Replication group overloaded exception code.

Reduce load or increase resources for the replication group.

IGN-REST-1

Cluster has not yet been initialized or the node is in the process of stopping.

Initialize the cluster and restart the node.

IGN-SECONDARY_STORAGE-1

Failure during sending message to the secondary storage.

Check network connectivity between primary and secondary storage nodes. Verify that the secondary storage nodes are accessible and running. Check cluster logs for communication errors.

IGN-SECONDARY_STORAGE-2

Failure while trying to start secondary storage replication manager.

Check secondary zone configuration. Ensure that nodes of the secondary zones are available in the cluster. Check logs for resource allocation issues.

IGN-SECONDARY_STORAGE-3

Failed to initialize secondary storage bridge.

Check network connectivity. Check cluster logs for communication errors.

IGN-SECONDARY_STORAGE-4

Failed to get secondary storage.

Retry the operation after verifying storage availability. Check cluster logs for communication errors.

IGN-SECONDARY_STORAGE-5

Failed to write data into secondary storage.

Check available disk space. Verify write permissions for the storage location. Check network connectivity. Retry the write operation. Check cluster logs for communication errors.

IGN-SECONDARY_STORAGE-6

Failed to read data from secondary storage.

Check read permissions for the storage location. Verify network connectivity. Check data integrity. Ensure secondary storage is operational.

GG-SECURITY-1

General security context error.

Check the exception message for the error details.

GG-SECURITY-2

Security context is not set, but security is enabled.

Change your code to use secured threads.

GG-SECURITY-3

Failed to get job owner.

Check the exception message for additional information.

GG-SNAPSHOTS-1

Generic snapshot error.

Check the exception message for information on why the error occurred.

GG-SNAPSHOTS-2

Error indicating that a snapshot has been canceled.

Check the exception message for information on what caused the snapshot to stop.

GG-SNAPSHOTS-3

Error indicating that an illegal or inappropriate argument was provided.

Check the command arguments and correct the command.

GG-SNAPSHOTS-4

Error indicating an attempt to delete a snapshot that does not exist.

Make sure the snapshot exists before deleting.

GG-SNAPSHOTS-5

Error indicating that the special metadata file for the snapshot is missing, usually this error occurs during restoration attempt.

Ensure that the snapshot folder contains the required metadata file; the snapshot may be corrupted.

GG-SNAPSHOTS-6

Error indicating that no operation exists for the given ID. This error typically occurs when executing CLI commands.

Check and use the correct snapshot operation ID.

GG-SNAPSHOTS-7

Error indicating that one or more tables specified for inclusion in a snapshot do not exist.

Ensure that all specified tables exist before creating the snapshot.

GG-SNAPSHOTS-8

Error indicating that an invalid snapshot path name has been used in the configuration for creation or restoration. This occurs when specifying a non-existent path as the destination or source for a snapshot.

Verify and correct the snapshot path name according to the GridGain snapshot documentation. Ensure the path exists in the configuration.

GG-SNAPSHOTS-9

The specified encryption or decryption provider does not exist.

Verify that the parameter value matches the configured providers in the configuration.

GG-SNAPSHOTS-10

During restoration of a snapshot, one of the target table partitions did not have a primary replica. This means that either a long ongoing rebalance was under way or one of the target tables belonged to a distribution zone without data nodes.

Retry the request and, if the issue persists, check that the target distribution zones contain at least one data node.

IGN-SQL-1

Exception is thrown when a query doesn’t intend to return any rows (for example, a DML or a DDL query).

Change the request to not expect the result from the query.

IGN-SQL-2

Exception is thrown when the specified schema cannot be found.

Make sure you use the existing schema name.

IGN-SQL-3

Statement parsing error. This error is returned when an SQL statement string is not valid according to syntax rules.

Check the exception message and correct issues in the query.

IGN-SQL-4

Statement validation error. Although statement is grammatically correct, the semantic is in question. For example, this can happen when the statement refers to relations that do not exist or describes a prohibited action.

Check the exception message and correct the query.

IGN-SQL-5

Constraint violation error such as primary key violation or NOT NULL.

Check the exception message and correct the query.

IGN-SQL-6

Statement canceled error. Statement is canceled due to timeout, admin action, etc.

Check the exception message to find out the specific reason.

IGN-SQL-7

Runtime error. Errors caused by programming errors in SQL statement itself, such errors happen during statement execution. For example, this can be caused by numeric overflow errors or type conversion errors.

Check the exception message and fix the issue.

IGN-SQL-8

SQL engine was unable to map query on current cluster topology. This may be due to a variety of reasons, but most probably because of all nodes hosting certain system view or a table partition went offline.

Check the exception message. In most scenarios, you can rerun the query when the cluster is stable.

IGN-SQL-9

Execution of transaction control statement inside an external transaction is forbidden.

Do not use transaction control statements like BEGIN TRANSACTION or COMMIT in external transactions, including JDBC with disabled autocommit mode.

GG-MEMQUOTA-1

Disk spilling I/O error occurred.

See the exception message for details. Typically, this is caused either by disk I/O issues (not enough space, insufficient permissions etc.) or by an internal GridGain error.

GG-MEMQUOTA-2

Disk quota used for disk spilling has been exceeded.

Disable or increase the disk quota size using the sql.offloadingDataLimit configuration option.

GG-MEMQUOTA-3

Memory quota used for a query has been exceeded.

Rewrite the query to use less memory or increase the memory quota for the query using the sql.statementMemoryQuota configuration option.

GG-MEMQUOTA-4

Node memory quota exceeded.

Increase node memory quota using the sql.nodeMemoryQuota configuration option.

IGN-STORAGE-1

A disaster has occurred, followed by an attempt to recover from the disaster. This caused inconsistent index state in the cluster metadata.

Wait until the index is rebuilt automatically.

IGN-STORAGE-2

A disaster has occurred, which led to data corruption in the persistent storage.

Restore the data from a backup or introduce a new node instead of the broken one (this may lead to data loss if the replication factor is too low).

IGN-TBL-1

Table already exists.

Make sure to use the table name that does not exist on the cluster.

IGN-TBL-2

Table not found.

Check the table name and, if necessary, create it.

IGN-TBL-3

Column already exists.

Make sure to use the column name that does not exist in the table.

IGN-TBL-4

Column not found.

Check the column name and, if necessary, create it.

IGN-TBL-5

Schema version mismatch.

The request uses a different schema than the table.

IGN-TBL-6

Partition type not supported.

Use a supported partition type.

IGN-TX-1

Default error for transaction state storage.

General error, check the logs and take action depending on the cause. Make sure there are no disk errors.

IGN-TX-2

Storage is stopped.

Storage is stopped due to the node stop or replica stop. No action is required unless this behavior is unexpected. Otherwise check the log for details.

IGN-TX-3

Unexpected transaction state on state change.

This can happen when trying to commit an already aborted transaction or roll back a committed one. No action is required.

IGN-TX-4

Failed to acquire a lock on a key due to a conflict.

The lock is held by another transaction. Retry the operation or change the deadlock prevention policy.

IGN-TX-5

Failed to acquire a lock on a key within the timeout.

The lock is held by another transaction. Make sure that the other transaction is not hanging, kill it if necessary; or retry the operation.

IGN-TX-6

Failed to commit a transaction.

Take actions depending on the cause. Make sure that all partitions in the cluster have a majority of nodes online in their groups.

IGN-TX-7

Failed to roll back a transaction.

Take actions depending on the cause. Make sure that all partitions in the cluster have a majority of nodes online in their groups.

IGN-TX-8

Failed to put read-write operation into read-only transaction.

The read-write operations within read-only transactions are not possible.

IGN-TX-9

Transaction state storage rebalancing error.

Fix the cause of the rebalancing error, make sure there are no disk errors.

IGN-TX-10

Failed to create a read-only transaction with a timestamp older than the data available in the tables.

Retry the transaction with newer read timestamp. Increase data availability time.

IGN-TX-11

Failure due to an incompatible schema change.

The transaction tried to access data within incompatible schema. Retry the transaction.

IGN-TX-12

Failure due to primary replica expiration.

Retry the transaction. Make sure there are no node failures, network issues or JVM/GC pauses that can cause the primary replica expiration.

IGN-TX-13

Transaction already finished.

This can be caused by any operation within a finished (committed or aborted) transaction. Doesn’t require any specific action.

IGN-TX-14

Failure due to a stale operation of a completed transaction.

Error that occurs when a stale operation of a transaction is detected. Try to rerun the transaction, if necessary.

IGN-TX-15

Error occurred when trying to execute an operation in a read-only transaction on a node that has already destroyed data for read timestamp of the transaction.

Retry the transaction with newer read timestamp. Increase data availability time.

IGN-TX-16

Operation failed because the transaction is already finished with timeout.

Verify transaction timeout settings and ensure operations are executed before the transaction expires.