You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Pavel Kovalenko (JIRA)" <ji...@apache.org> on 2018/07/25 17:04:00 UTC

[jira] [Created] (IGNITE-9082) Throwing checked exception during tx commit without node stopping leads to data corruption

Pavel Kovalenko created IGNITE-9082:
---------------------------------------

             Summary: Throwing checked exception during tx commit without node stopping leads to data corruption
                 Key: IGNITE-9082
                 URL: https://issues.apache.org/jira/browse/IGNITE-9082
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: 2.6, 2.5, 2.4
            Reporter: Pavel Kovalenko
             Fix For: 2.7


If we get checked exception during tx commit on a primary node and this exception is not supposed to be handled as NodeStopping OR doesn't lead to node stop using Failure Handler, in this case, we may get data loss on a node which is a backup node for this tx.

Possible solution:
If we get any checked or unchecked exception during tx commit we should stop this node after that to prevent further data loss.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)