[
https://issues.apache.org/jira/browse/IGNITE-10572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712968#comment-16712968
]
ASF GitHub Bot commented on IGNITE-10572:
-----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5608
IGNITE-10572: Fix races in mvcc invokeAll().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10572
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5608.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 #5608
----
commit 118c2d842d557f85f6aa98d878bad4fc809e500b
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date: 2018-12-07T14:32:16Z
IGNITE-10572: Fix races on invokeAll().
----
> MVCC TX: Possible race on invokeAll operations
> ----------------------------------------------
>
> Key: IGNITE-10572
> URL: https://issues.apache.org/jira/browse/IGNITE-10572
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Igor Seliverstov
> Assignee: Andrew Mashenkov
> Priority: Major
> Fix For: 2.8
>
>
> see {{GridNearTxEnlistFuture#checkResponse}} method.
> 1) race on result creation - two threads may see {{this.res == null}} and
> just set their values, result is partially lost
> 2) race on success flag set - just set false flag may be overwritten by
> concurrent successful response checking operation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
