[
https://issues.apache.org/jira/browse/IGNITE-8080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420365#comment-16420365
]
ASF GitHub Bot commented on IGNITE-8080:
----------------------------------------
GitHub user Jokser opened a pull request:
https://github.com/apache/ignite/pull/3721
IGNITE-8080 Avoid updating tx entries twice
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8080
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3721.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3721
----
commit 9b0adbdf4a251badb7cb0868c598a6a40c6e4a3e
Author: Pavel Kovalenko <jokserfn@...>
Date: 2018-03-30T10:36:30Z
IGNITE-8080 Avoid updating tx entries twice if near entry update throws
EntryRemovedException.
----
> Partition update counter can be incremented twice in case of transaction
> commit and near cache enabled
> ------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-8080
> URL: https://issues.apache.org/jira/browse/IGNITE-8080
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.4
> Reporter: Pavel Kovalenko
> Assignee: Pavel Kovalenko
> Priority: Minor
> Fix For: 2.5
>
>
> Problem:
> * Commit local transaction (IgniteTxLocalAdapter#userCommit())
> * TxEntry is updated and update counter is incremented.
> * Try to update near cache entry and this operation can throw
> GridCacheEntryRemovedException
> * In case when exception is thrown we start to update TxEntry again and
> update counter will be incremented twice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
