[
https://issues.apache.org/jira/browse/IGNITE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695058#comment-16695058
]
Ignite TC Bot commented on IGNITE-10047:
----------------------------------------
{panel:title=Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Inspections: Core{color} [[tests 0 BuildFailureOnMetric
|https://ci.ignite.apache.org/viewLog.html?buildId=2371599]]
{panel}
[TeamCity Run All
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2369147&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
