You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2016/08/02 19:24:20 UTC

[jira] [Commented] (IGNITE-3321) Address possible data corruption in Persistent Store implementations

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

Konstantin Boudnik commented on IGNITE-3321:
--------------------------------------------

I thought there was a bug opened for that, no? If not - it sure should be.

> Address possible data corruption in Persistent Store implementations
> --------------------------------------------------------------------
>
>                 Key: IGNITE-3321
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3321
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>    Affects Versions: 1.6
>         Environment: any
>            Reporter: Alexandre Boudnik
>            Assignee: Alexandre Boudnik
>            Priority: Critical
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> When records from partitions on different nodes are committed, each node uses its own SQL connection. It is possible that one of DML statements will fail on one of the connections, while others have committed successfully.
> And we need to make a very hard decision:
> - If we ignore fail then we will lose some changes.
> - If we throw an exception we will make inconsistent changes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)