[
https://issues.apache.org/jira/browse/IGNITE-10047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16691532#comment-16691532
]
Roman Kondakov commented on IGNITE-10047:
-----------------------------------------
[~gvvinblade], as we discussed, in addition to your comments I'll unbind MVCC
coordinator appointment from PME as much as possible:
# Move mvcc coordinator appointment from Discovery manager to Mvcc processor.
# Move mvcc coordinator initialization from
{{GridDhtPartitionsExchangeFuture}} to Mvcc processor.
# Remove active queries list from {{GridDhtPartitionsSingleMessage}} and sent
these list directly to mvcc coordinator.
> 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)
