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

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2015/12/07 13:08:10 UTC

[jira] [Resolved] (IGNITE-2083) EntryProcessor is called twice on primary node in transactional cache

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

Semen Boikov resolved IGNITE-2083.
----------------------------------
    Resolution: Fixed

Fixed in 1.5 as suggested by Alexey (commit 9a14d64).

> EntryProcessor is called twice on primary node in transactional cache
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-2083
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2083
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>            Reporter: Valentin Kulichenko
>            Assignee: Semen Boikov
>            Priority: Critical
>             Fix For: 1.5
>
>
> Issue is described in details here: http://apache-ignite-developers.2346864.n4.nabble.com/EntryProcessor-invoked-twice-td5494.html
> Looks like that this can be optimized, at least for {{REPEATABLE_READ}} transactions.



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