Handling Exceptions
This section outlines basic exceptions that can be generated by GridGain 9 and provides basic instructions for handling them.
Finding Stack Trace Information
When the exception happens, GridGain 9 provides a UUID of the specific exception, but not a full stack trace. For a full stack trace, check cluster logs.
Common Exceptions
| Exception | Description |
|---|---|
|
Operation was stopped because node is stopping. |
|
Operation was stopped because the component is not started. |
|
Operation failed because an illegal argument or argument in a wrong format has been passed. |
|
Operation failed because SSL could not be configured. |
|
Operation failed because a node has left the cluster. |
|
Operation failed because the cursor is already closed. |
|
An error occurred while closing resources. |
|
An error occurred while marshalling or unmarshalling objects. |
|
The method cannot return a null value. |
|
Internal error has occurred. |
Table Exceptions
| Exception | Description |
|---|---|
|
Table already exists. |
|
Table not found. |
|
Column already exists. |
|
Column not found. |
|
Table is currently stopping. |
|
Table definition not correct. |
|
Schema version mismatch. |
|
Partition type not supported. |
Client Exceptions
| Exception | Description |
|---|---|
|
Connection to client failed. |
|
An issue occurred with connection protocol. |
|
Incompatible protocol version. |
|
Failed to find the table by ID. |
|
An error occurred during authentication. |
|
An error occurred during authorization. |
|
An error occurred with client configuration. |
|
Cluster ID mismatch. |
|
Client SSL configuration is not valid. |
|
Invalid header in client handshake message. |
SQL Exceptions
| Exception | Description |
|---|---|
|
Failed to read response from a query that does not return rows. |
|
Schema not found error. |
|
Statement parsing error. SQL string is not grammatically valid. |
|
Statement validation error. SQL string is not semantically valid or contains prohibited operations. |
|
Constraint violation error, for example, primary key violation. |
|
Statement got cancelled. |
|
Runtime error. Usually caused an SQL error, for example numeric overflow. |
|
Planning timed out without finding any valid plan. |
|
SQL engine was unable to map query on current cluster topology. Most likely, the partition or view is not available because all nodes containing it are offline. |
|
Execution of transaction control statement inside an external transaction is forbidden. |
Meta Storage Exceptions
| Exception | Description |
|---|---|
|
Failed to start the underlying key value storage. |
|
Failed to restore the underlying key value storage. |
|
Failed to compact the underlying key value storage. |
|
Failed to perform an operation on the underlying key value storage. |
|
Failed to perform an operation within a specified time period. |
Index Exceptions
| Exception | Description |
|---|---|
|
Invalid index definition. |
|
Failed to find the specified index. |
|
Specified index already exists. |
Transactions Exceptions
| Exception | Description |
|---|---|
|
Default error for transaction state storage. |
|
Transaction state storage is stopped. |
|
Unexpected transaction state on state change. |
|
Failed to acquire a lock on a key due to a conflict. |
|
Failed to acquire a lock on a key within the timeout. |
|
Failed to commit a transaction. |
|
Failed to roll back a transaction. |
|
Failed to put read-write operation into read-only transaction. |
|
Replica is not ready to handle a request. |
|
Transaction state storage rebalancing error. |
|
Failed to create a read-only transaction with a timestamp older than the data available in the tables. |
|
Failure due to an incompatible schema change. |
|
Failure due to primary replica expiration. |
|
Transaction already finished. |
|
Failure due to a stale operation of a completed transaction. |
|
Failure due to cache operations enlisted into table transaction or vice versa. |
Replicator Exceptions
| Exception | Description |
|---|---|
|
Default error for the replication procedure. |
|
Replica with the same identifier already exists. |
|
Timeout has happened during the replication procedure. |
|
The replication level tried to handle an unsupported request. |
|
Replica is not ready to handle the request. |
|
Replica is not the current primary replica. |
|
Failed to close cursor. |
|
Replica is already stopping. |
|
Replication safe time reordering. |
Storage Exceptions
| Exception | Description |
|---|---|
|
Default error code for storage exceptions. |
|
Failed to create a directory. |
|
Failed to perform operation because the storage is closed. |
|
Storage rebalancing error. |
|
Failed to perform operation because the storage is destroyed. |
|
Error reading from an index that has not yet been built. |
Distribution Zone Exceptions
| Exception | Description |
|---|---|
|
Distribution zone is not found. |
Network Exceptions
| Exception | Description |
|---|---|
|
Unresolvable consistent ID. |
|
Port is already in use. |
|
Recipient node has left the physical topology. |
|
Could not resolve address. |
Node Configuration Exceptions
| Exception | Description |
|---|---|
|
Failed to read configuration. |
|
Failed to create a configuration file. |
|
Failed to write configuration. |
|
Failed to parse configuration. |
Code Deployment Exceptions
| Exception | Description |
|---|---|
|
Access attempt to a non-existing deployment unit. |
|
Duplicate deployment unit. |
|
Deployment unit content read error. |
|
Deployment unit is unavailable for computing. |
Garbage Collector Exceptions
| Exception | Description |
|---|---|
|
Garbage collector closed. |
Authentication Exceptions
| Exception | Description |
|---|---|
|
Authentication error caused by unsupported authentication type. |
|
Authentication error caused by invalid credentials. |
|
Basic authentication provider is not found. |
Compute Exceptions
| Exception | Description |
|---|---|
|
Classpath error. |
|
Class loader error. |
|
Failed to initialize the job class. |
|
Execution queue overflow. |
|
Compute job status transition error. |
|
Failed to cancel compute job. |
|
Compute job result not found. |
|
Compute job state cannot be retrieved. |
|
Compute job failed. |
|
Failed to change job priority, because compute job was not found. |
|
Failed to change job priority, because compute job is already executing. |
|
Failed to resolve primary replica for colocated execution. |
|
Failed to change job priority. |
|
Specified node is not found in the cluster. |
|
Compute job owner cannot be retrieved. |
Catalog Exceptions
| Exception | Description |
|---|---|
|
Command to the catalog has not passed the validation. See exception message for details. |
Placement Driver Exceptions
| Exception | Description |
|---|---|
|
Primary replica await timeout error. |
|
Primary replica await error. |
Critical Workers Exceptions
| Exception | Description |
|---|---|
|
System worker does not update its heartbeat for a long time. |
|
System-critical operation timed out. |
Disaster Recovery Exceptions
| Exception | Description |
|---|---|
|
Partition ID is not in valid range. |
|
Nodes were not found. |
|
Failed to recover partition states. |
|
Cluster is under load. |
© 2024 GridGain Systems, Inc. All Rights Reserved. Privacy Policy | Legal Notices. GridGain® is a registered trademark of GridGain Systems, Inc.
Apache, Apache Ignite, the Apache feather and the Apache Ignite logo are either registered trademarks or trademarks of The Apache Software Foundation.