[IGNITE-5874] Store TTL expire times in B+ tree on per-partition basis

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.7
• Component/s: cache, persistence
• Labels: MakeTeamcityGreenAgain
• Assignee: Andrey Mashenkov
• Reporter: Ivan Rakov
• Created: 28/Jul/17 17:56
• Updated: 27/Sep/18 12:16
• Resolved: 11/May/18 15:52

Description

TTL expire times for entries are stored in PendingEntriesTree, which is singleton for cache. When expiration occurs, all system threads iterate through the tree in order to remove expired entries. Iterating through single tree causes contention and perfomance loss.
Related performance issue: https://issues.apache.org/jira/browse/IGNITE-5793
We should keep instance of PendingEntriesTree for each partition, like we do for CacheDataTree.

Issue Links

• Blocked: IGNITE-7742 AssertionError in IgniteCacheOffheapManagerImpl when Iterate Cache with expire policy and persistence
• blocks: IGNITE-9707 TouchedExpiryPolicy with persistent on atomic cache, update TTL without lock
• blocks: IGNITE-8046 New flaky tests added in JettyRestProcessorAuthenticationSelfTest
• blocks: IGNITE-7778 User's authentication data must be persisted on cluster with disabled persistence
• causes: IGNITE-8659 Wrong FreeList usage in PendingTree may lead to page corruption.
• causes: IGNITE-8681 Using ExpiryPolicy with persistence causes significant slowdown.
• is duplicated by: IGNITE-6959 Split a ttl index tree by partition
• is related to: IGNITE-6815 "Unexpected exception during cache update" via NullPointerException thrown using TouchedExpiryPolicy
• is related to: IGNITE-8295 Possible deadlock on partition eviction.
• is related to: IGNITE-8483 Per partition TTL pending tree for in-memory caches.
• relates to: IGNITE-6964 Ignite restart with PDS enabled may cause delays in TTL cleanup worker
• links to: CR-593
• links to: Git pull request #3231
• links to: TC 'Run All'