[
https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771891#comment-16771891
]
Igor Seliverstov edited comment on IGNITE-10693 at 2/19/19 12:51 PM:
---------------------------------------------------------------------
After fixing mapping logic the affected tests become much stable. However some
failures are still there (inconsistent reads on unstable topology). It can be
easily reproduced increasing keys count in test scenarios. At now everything
points to the fact the root cause is an issue in rebalance logic. Need to put
the task on hold until IGNITE-10561 is resolved.
was (Author: gvvinblade):
At now everything points to the fact the root cause is an issue in rebalance
logic. Need to put the task on hold until IGNITE-10561 is resolved.
> 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
> Assignee: Igor Seliverstov
> Priority: Major
> Labels: failover, mvcc_stabilization_stage_1
> Fix For: 2.8
>
> Time Spent: 10m
> 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
(v7.6.3#76005)