You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/10/15 07:55:00 UTC
[jira] [Created] (IGNITE-9880) Document MVCC write conflict
exceptions
Vladimir Ozerov created IGNITE-9880:
---------------------------------------
Summary: Document MVCC write conflict exceptions
Key: IGNITE-9880
URL: https://issues.apache.org/jira/browse/IGNITE-9880
Project: Ignite
Issue Type: Task
Components: documentation
Reporter: Vladimir Ozerov
Assignee: Artem Budnikov
Fix For: 2.7
When an entry is read (1) inside a transaction and then updated (2), there is a chance that concurrent transaction will modify that entry in between (1) and (2). In this case an error is thrown from the first transaction when action (2) is performed and transaction is marked as "rollback only". User need to re-try the whole transaction in this case.
When native APi is used, then {{CacheException}} is thrown with special message {{Cannot serialize transaction due to write conflict (transaction is marked for rollback)}}. This will be changed in future (AI 2.8|) - special exception type will be thrown.
When JDBC or ODBC are used, then special SQLSTATE code 40001 (aka "Serialization failure") is propagated to user.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)