[
https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Muzafarov updated IGNITE-10693:
-------------------------------------
Fix Version/s: (was: 2.8)
2.9
> MVCC TX: Random server restart tests became failed
> --------------------------------------------------
>
> Key: IGNITE-10693
> URL: https://issues.apache.org/jira/browse/IGNITE-10693
> Project: Ignite
> Issue Type: Bug
> Components: mvcc
> Reporter: Igor Seliverstov
> Priority: Major
> Labels: failover, mvcc_stability
> Fix For: 2.9
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> [one|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=7945125576049372508&branch=%3Cdefault%3E&tab=testDetails],
>
> [two|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=8412476034648229784&branch=%3Cdefault%3E&tab=testDetails],
>
> [three|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=254244004184327163&branch=%3Cdefault%3E&tab=testDetails],
> all these tests became failed after IGNITE-9630 has been merged to master.
> Seems there is an issue in partition calculating mechanism on unstable
> topology. I suppose the algorithm uses partitions on nodes just become
> primary while the partitions are in moving state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
