[
https://issues.apache.org/jira/browse/IGNITE-9663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654188#comment-16654188
]
ASF GitHub Bot commented on IGNITE-9663:
----------------------------------------
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5018
IGNITE-9663: Data node failure can cause TX hanging.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9663
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5018.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 #5018
----
commit 02b9a43df59c6c3b5ed5424d462bb21383e4da9b
Author: rkondakov <kondakov87@...>
Date: 2018-10-17T18:56:10Z
IGNITE-9663: Data node failure can cause TX hanging. WIP
----
> MVCC: Data node failure can cause TX hanging.
> ---------------------------------------------
>
> Key: IGNITE-9663
> URL: https://issues.apache.org/jira/browse/IGNITE-9663
> Project: Ignite
> Issue Type: Bug
> Components: cache, mvcc
> Reporter: Andrew Mashenkov
> Assignee: Roman Kondakov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Next test hangs due to a bug:
> CacheMvccTransactionsTest.testPutAllGetAll_ClientServer_Backups1_Restart_Scan
> Possibly, it is caused with a race in MvccTracker and can be partially fixed
> in [#1] or
> we have a bug in TX mapping in enlist phase on unstable topology.
>
> I've tried to avoid races in Tracker and see TX hanged awaiting PME that
> version has just been completed. This need to be investigated.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-9428
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
