[
https://issues.apache.org/jira/browse/IGNITE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679937#comment-16679937
]
ASF GitHub Bot commented on IGNITE-10047:
-----------------------------------------
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5353
IGNITE-10047: Wrong MVCC coordinator assignment when multiple nodes failed
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10047
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5353.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 #5353
----
commit 6c364e04d9ad8519035662852c496445d2900042
Author: rkondakov <kondakov87@...>
Date: 2018-10-31T14:23:24Z
IGNITE-10047: Wrong coordinator assignment when two or more oldest nodes
fail.
----
> MVCC: Wrong coordinator assignment when two oldest nodes fail.
> --------------------------------------------------------------
>
> Key: IGNITE-10047
> URL: https://issues.apache.org/jira/browse/IGNITE-10047
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Roman Kondakov
> Assignee: Roman Kondakov
> Priority: Major
> Fix For: 2.8
>
>
> Reproducer:
> {{CacheContinuousQueryFailoverMvccTxSelfTest#testLeftPrimaryAndBackupNodes}}.
> This test can sporadically hangs when topology is unstable.
> The problem here is when two oldest nodes A and B failed, other nodes elect B
> node as a new coordinator despite it is down. This happens because the new
> mvcc coordinator is assigned in {{GridDhtPartitionsExchangeFuture#init}}
> method which is called only ones in case of multiple nodes fail
> simultaneously.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
