[
https://issues.apache.org/jira/browse/IGNITE-29114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18124437#comment-18124437
]
Ignite TC Bot commented on IGNITE-29114:
----------------------------------------
{panel:title=Branch: [pull/13659/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13659/head] Base: [master] : New Tests
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Basic 3{color} [[tests
1|https://ci2.ignite.apache.org/viewLog.html?buildId=9395438]]
* {color:#013220}IgniteBasicWithPersistenceTestSuite:
MasterKeyChangeTest.testCoordinatorFailsBetweenPrepareAndPerform - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9395581&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9395581
rerunBuildIds=none{color}
> Fix chained distributed processes hang when the coordinator leaves between
> phases
> ---------------------------------------------------------------------------------
>
> Key: IGNITE-29114
> URL: https://issues.apache.org/jira/browse/IGNITE-29114
> Project: Ignite
> Issue Type: Bug
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Major
> Fix For: 2.19
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> A distributed process that starts the next phase from its finish closure
> relies on {{{}U.isLocalNodeCoordinator{}}}, which is checked on each node
> when the full message arrives. If the coordinator leaves after sending the
> full message but before starting the next phase, no other node starts it, so
> the operation (master key change, cache group key change, snapshot check and
> restore, rolling upgrade finalization) hangs forever. The coordinator check
> is also made against the discovery ring state, which is not aligned with the
> discovery events order, so two nodes may consider themselves the coordinator
> at the same time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
