[
https://issues.apache.org/jira/browse/IGNITE-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16432488#comment-16432488
]
Dmitriy Pavlov commented on IGNITE-5874:
----------------------------------------
I've found suspicious tests started to fail in this branch and continued after
restart:
- IgniteAllBaselineNodesOnlineFullApiSelfTest.testWithSkipStoreTx
- IgniteOfflineBaselineNodeFullApiSelfTest.testWithSkipStoreTx
- IgniteOnlineNodeOutOfBaselineFullApiSelfTest.testWithSkipStoreTx
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePds2&branch=pull%2F3231%2Fhead&tab=buildTypeStatusDiv
Is it related to these changes?
> 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)
