[IGNITE-8503] Fix wrong GridCacheMapEntry startVersion initialization.

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7
• Component/s: cache, persistence
• Labels: MakeTeamcityGreenAgain Muted_test tck
• Assignee: Andrey Mashenkov
• Reporter: Dmitry Pavlov
• Created: 15/May/18 16:55
• Updated: 22/Jun/18 16:39
• Resolved: 22/Jun/18 16:39

Description

GridCacheMapEntry initialize startVersion in wrong way.
This leads to IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart failure and reason is "Entry which should be expired by TTL policy is available after grid restart."

 

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.

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

https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=5798755758125626876&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E

Issue Links

• relates to: IGNITE-8548 Make Apache Ignite JCache 1.1 specification compliant
• links to: GitHub Pull Request #4141
• links to: TC run results