[jira] [Created] (IGNITE-8503) IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (IGNITE-8503) IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart

Anton Vinogradov (Jira)
Dmitriy Pavlov created IGNITE-8503:
--------------------------------------

             Summary: IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart
                 Key: IGNITE-8503
                 URL: https://issues.apache.org/jira/browse/IGNITE-8503
             Project: Ignite
          Issue Type: Improvement
          Components: persistence
            Reporter: Dmitriy Pavlov


Test was added during https://issues.apache.org/jira/browse/IGNITE-5874 development.

This test restarts grid and checks all entries are not present in grid.

But with high possiblity one from 7000 entries to be expired is resurrected instead and returned by cache get.

{noformat}
After timeout {{

>>>
>>> Cache memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0, cache=expirableCache]
>>>  Cache size: 0
>>>  Cache partition topology stats [igniteInstanceName=db.IgnitePdsWithTtlTest0, grp=group1]
>>>
>>> Cache event manager memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0, cache=expirableCache, stats=N/A]
>>>
>>> Query manager memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0, cache=expirableCache]
>>>   threadsSize: 0
>>>   futsSize: 0
>>>
>>> TTL processor memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0, cache=expirableCache]
>>>   pendingEntriesSize: 0
}} After timeout
{noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)