ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9082) Throwing checked exception during tx commit without node stopping leads to data corruption
Date Thu, 18 Oct 2018 12:02:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-9082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16655114#comment-16655114
] 

ASF GitHub Bot commented on IGNITE-9082:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/4809


> 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.4, 2.5, 2.6
>            Reporter: Pavel Kovalenko
>            Assignee: Alexei Scherbakov
>            Priority: Major
>             Fix For: 2.8
>
>
> 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)

Mime
View raw message