You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2017/08/09 12:48:00 UTC

[jira] [Updated] (IGNITE-6011) EntryProcessor can make data inconsistent if fails on TX cache.

     [ https://issues.apache.org/jira/browse/IGNITE-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Mashenkov updated IGNITE-6011:
-------------------------------------
    Attachment: EntryProcessorBug.java

> EntryProcessor can make data inconsistent if fails on TX cache.
> ---------------------------------------------------------------
>
>                 Key: IGNITE-6011
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6011
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Andrew Mashenkov
>         Attachments: EntryProcessorBug.java
>
>
> I'd expect that with FULL_SYNC write mode and TX cache data always be consistent.
> And if EntryProcessor fails on primary (or backup) node and pass on backup (or primary) then whole transaction will be rolled back.
> But looks like it is not true, I observe old value on node where EP has failed and new value on other nodes.
> PFA repro attached.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)