You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2019/03/12 10:37:00 UTC
[jira] [Commented] (IGNITE-10693) MVCC TX: Random server restart
tests became failed
[ https://issues.apache.org/jira/browse/IGNITE-10693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16790425#comment-16790425 ]
Andrew Mashenkov commented on IGNITE-10693:
-------------------------------------------
Looks like issues wasn't fixed as TC tests still fails sporadically after merge with IGNITE-10561.
Possibly, mapping is not (the only) issue that causes test failures.
I've fixed few collection usage issues and revert unrelated changes in tests in my PR.
We have to verify mapping logic (correctness) and benchmark this changes (performance),
then the PR can be merged if logic is correct and performance improved, otherwise the PR should be declined.
> 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: Andrew Mashenkov
> Priority: Major
> Labels: failover, mvcc_stability
> Fix For: 2.8
>
> Time Spent: 20m
> 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)