[jira] [Updated] (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 ] Valentin Kulichenko updated IGNITE-2083: Labels: important (was: ) > 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 >Priority: Critical > Labels: important > 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)
[jira] [Updated] (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 updated IGNITE-2083: - Fix Version/s: (was: 1.6) 1.5 > 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)