ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Igor Rudyak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3321) Address possible data corruption in Persistent Store implementations
Date Tue, 02 Aug 2016 21:20:20 GMT

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

Igor Rudyak commented on IGNITE-3321:
-------------------------------------

Not sure about the bug opened for the issue. Just know that two CacheStore implementations
(JDBC and Cassandra based) are affected by this.

> 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)

Mime
View raw message