[ https://issues.apache.org/jira/browse/IGNITE-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389454#comment-16389454 ]
Dmitriy Pavlov commented on IGNITE-7898: ---------------------------------------- Hi [~Jokser], thank you for continuing to improve Ignite. please consider closing IGNITE-5148 if your new change will help to solve the problem > IgniteCachePartitionLossPolicySelfTest is flaky on TC > ----------------------------------------------------- > > Key: IGNITE-7898 > URL: https://issues.apache.org/jira/browse/IGNITE-7898 > Project: Ignite > Issue Type: Bug > Components: cache > Affects Versions: 2.4 > Reporter: Pavel Kovalenko > Assignee: Pavel Kovalenko > Priority: Major > Labels: MakeTeamcityGreenAgain > > Affected tests: > testReadOnlyAll > testReadWriteSafe > Exception: > {code:java} > junit.framework.AssertionFailedError: Failed to find expected lost partition > [exp=0, lost=[]] > at > org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:219) > at > org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:166) > at > org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:114) > {code} > The problem of failure: > After we prepare topology and shutdown the node containing lost partition we > start to check it immediately on all nodes (cache.lostPartitions() method). > Sometimes we invoke this method on client node where last PME is not even > started and getting empty list of lost partitions because we haven't received > it yet on PME. > Possible solution: > Wait for PME finishing on all nodes (including client) before start to check > for lost partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)