[
https://issues.apache.org/jira/browse/IGNITE-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16439377#comment-16439377
]
Dmitriy Pavlov commented on IGNITE-5874:
----------------------------------------
>From latest runs
Suspicious failures are:
Ignite Platform .NET Long Running [ tests 1 ] exe:
CacheTest.TestGetMultithreadedSingleClient (master fail rate 0,0%)
Ignite PDS [2] [ tests 0 TIMEOUT , Exit Code warn 12 ]
IgnitePdsContinuousRestartTestWithExpiryPolicy.testRebalncingDuringLoad_10_10_1_1
(last started)
> Store TTL expire times in B+ tree on per-partition basis
> --------------------------------------------------------
>
> Key: IGNITE-5874
> URL: https://issues.apache.org/jira/browse/IGNITE-5874
> Project: Ignite
> Issue Type: Improvement
> Components: cache, persistence
> Affects Versions: 2.1
> Reporter: Ivan Rakov
> Assignee: Andrew Mashenkov
> Priority: Major
> Fix For: 2.5
>
> Attachments: IgnitePdsWithTtlTest.java
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
