[jira] [Assigned] (IGNITE-7898) IgniteCachePartitionLossPolicySelfTest is flaky on TC

["Pavel Kovalenko (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-7898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pavel Kovalenko reassigned IGNITE-7898:
---------------------------------------

    Assignee: Alexey Goncharuk  (was: Pavel Kovalenko)

Fix is ready. Changes are only in test (only Cache5 suite is affected).
TC Run: https://ci.ignite.apache.org/viewLog.html?buildId=1135150&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_IgniteCache5
PR: https://github.com/apache/ignite/pull/3626

> 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: Alexey Goncharuk
>            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)