You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by " Kirill Sizov (Jira)" <ji...@apache.org> on 2023/12/28 10:49:00 UTC

[jira] [Created] (IGNITE-21173) Repeated call to commit/abort should not emit exceptions

 Kirill Sizov created IGNITE-21173:
--------------------------------------

             Summary: Repeated call to commit/abort should not emit exceptions
                 Key: IGNITE-21173
                 URL: https://issues.apache.org/jira/browse/IGNITE-21173
             Project: Ignite
          Issue Type: Task
            Reporter:  Kirill Sizov


As per the docs,

??A commit of a completed or ending transaction has no effect and always succeeds when the transaction is completed.??

At the moment, if a first call to commit/abort fails with a exception, the subsequent ones will fail with the same exception. 

*Definition of Done*

1. Subsequent calls to commit/abort should succeed.
2. The tests should reflect this change
3. If a transaction is being committed, but the finishing logic decides to abort this transaction (due to primary replica expiration), the commit call with fail with {{TransactionAlreadyFinishedException}}. 
The exception should be renamed to {{MismatchingTransactionOutcomeException}}, as it is thrown when the real outcome is different from the one we provide as a parameter.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)