This is an automated email from the ASF dual-hosted git repository.
sk0x50 pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/ignite-3.git
The following commit(s) were added to refs/heads/main by this push:
new c8948ea1862 IGNITE-28064 Add unknown error code (#7704)
c8948ea1862 is described below
commit c8948ea18627489f81f5efaaf41864b13b82639c
Author: jinxxxoid <[email protected]>
AuthorDate: Fri Apr 3 13:07:34 2026 +0400
IGNITE-28064 Add unknown error code (#7704)
---
docs/docs/configure-and-operate/operations/handle-exceptions.md | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/docs/docs/configure-and-operate/operations/handle-exceptions.md
b/docs/docs/configure-and-operate/operations/handle-exceptions.md
index fccc1714d00..835f119f32b 100644
--- a/docs/docs/configure-and-operate/operations/handle-exceptions.md
+++ b/docs/docs/configure-and-operate/operations/handle-exceptions.md
@@ -258,3 +258,9 @@ When the exception happens, Apache Ignite provides a UUID
of the specific except
| `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. |
+
+## Unknown Error Codes
+
+| Exception Code | Description | Recommended Action |
+|---|---|---|
+| `UNKNOWN-UNKNOWN{groupCode}-{errorCode}` | The client received an error code
it does not recognize. This occurs when an older client connects to a newer
server version that introduced error codes unknown to the client. | Update the
client to a version compatible with the server to receive proper error details.
Check the server logs for the full error context. |
