[
https://issues.apache.org/jira/browse/IGNITE-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517539#comment-14517539
]
Andrey Gura edited comment on IGNITE-728 at 7/23/15 9:48 AM:
-------------------------------------------------------------
Actually it is performance issue. There is only one thread ({{CleanupWorker}})
that handles expirations and many threads adding entires. Thus it is possible
trhat OOM will be thrown becuase expired entries still exists in the cache. Now
eviction handling performs not only by {{CleanupWorker}} but for each cache
operation by updating thread (see {{GridCacheUtils.unwindEvicts}}).
Tests fixed.
was (Author: agura):
Tests fixed.
> Need to reimplement CREATE-TIME-TTL as eviction policy
> ------------------------------------------------------
>
> Key: IGNITE-728
> URL: https://issues.apache.org/jira/browse/IGNITE-728
> Project: Ignite
> Issue Type: Sub-task
> Components: cache, streaming
> Reporter: Dmitriy Setrakyan
> Assignee: Andrey Gura
> Priority: Blocker
> Fix For: sprint-4
>
> Attachments: ignite-728.patch, ignite-728.patch
>
>
> # We should treat eviction queue as a collection of fix-sized buckets.
> # Each bucket can be a list of entries.
> # Each bucket should keep a timestamp of when that bucket was crated.
> Whenever (currentTime - bucketCreateTime) > TTL, all the entries in the
> bucket get evicted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
