[IGNITE-5148] Unstable test IgniteCachePartitionLossPolicySelfTest testReadWriteSafe() seems to be flaky in 2.0

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 2.0
• Labels: MakeTeamcityGreenAgain test-fail
• Assignee: Pavel Vinokurov
• Reporter: Dmitry Pavlov
• Created: 03/May/17 12:07
• Updated: 16/Aug/18 12:05
• Resolved: 16/Aug/18 12:05

Description

Branch ignite 2.0:

org.apache.ignite.internal.processors.cache.distributed.
IgniteCachePartitionLossPolicySelfTest#testReadWriteSafe
locally each 10th launch failed with

junit.framework.AssertionFailedError: Failed to find expected lost partition [exp=0, lost=[]]

	at junit.framework.Assert.fail(Assert.java:57)
	at junit.framework.Assert.assertTrue(Assert.java:22)
	at junit.framework.TestCase.assertTrue(TestCase.java:192)
	at org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.verifyCacheOps(IgniteCachePartitionLossPolicySelfTest.java:234)
	at org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.checkLostPartition(IgniteCachePartitionLossPolicySelfTest.java:181)
	at org.apache.ignite.internal.processors.cache.distributed.IgniteCachePartitionLossPolicySelfTest.testReadWriteSafe(IgniteCachePartitionLossPolicySelfTest.java:131)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at junit.framework.TestCase.runTest(TestCase.java:176)
	at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1930)
	at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:125)
	at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1845)
	at java.lang.Thread.run(Thread.java:748)

Issue Links

• is related to: IGNITE-7898 IgniteCachePartitionLossPolicySelfTest is flaky on TC
• relates to: IGNITE-5078 Partition lost event is fired only on coordinator when partition loss policy is IGNORE
• relates to: IGNITE-9178 Partition lost event are not triggered if multiple nodes left cluster
• relates to: IGNITE-8746 EVT_CACHE_REBALANCE_PART_DATA_LOST event received twice on the coordinator node
• relates to: IGNITE-8912 PartitionLossPolicy.READ_ONLY_SAFE does not detect partition loss
• relates to: IGNITE-9264 Lost partitions raised twice if node left during previous exchange