[
https://issues.apache.org/jira/browse/IGNITE-2083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15041753#comment-15041753
]
Alexey Goncharuk commented on IGNITE-2083:
------------------------------------------
EntryProcessor invocation result is recorded in
IgniteTxEntry.entryProcessorCalculatedValue(), so I think for this case it can
be safely reused during the commit step, thus EntryProcessor will not be called
twice.
> 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)
