[
https://issues.apache.org/jira/browse/IGNITE-12002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philippe Anes updated IGNITE-12002:
-----------------------------------
Description:
Create an ignite client (in client mode false) and put some data (10k
entries/values) to it with very small expiration time (~20s) and TTL enabled.
Each time the thread is running it'll remove all the entries that expired, but
after few attempts this thread is not removing all the expired entries, some of
them are staying in memory and are not removed by this thread execution.
That means we got some expired data in memory, and it's something we want to
avoid.
Please can you confirm that is a real issue or just misuse/configuration of my
test?
Thanks for your feedback.
To reproduce:
Git repo: [https://github.com/panes/ignite-sample]
Run MyIgniteLoadRunnerTest.run() to reproduce the issue described on top.
(Global setup: Writing 10k entries of 64octets each with TTL 10s)
was:
Create an ignite client (in client mode false) and put some data (10k
entries/values) to it with very small expiration time (~20s) and TTL enabled.
Each time the thread is running it'll remove all the entries that expired, but
after few attempts this thread is not removing all the expired entries, some of
them are staying in memory and are not removed by this thread execution.
That means we got some expired data in memory, and it's something we want to
avoid.
Please can you confirm that is a real issue or just misuse/configuration of my
test?
Thanks for your feedback.
To reproduce:
Git repo: [https://github.com/panes/ignite-sample]
Run MyIgniteLoadRunnerTest.run() to reproduce the issues described on top.
(Global setup: Writing 10k entries of 64octets each with TTL 10s)
> [TTL] Some expired data remains in memory even with eager TTL enabled
> ---------------------------------------------------------------------
>
> Key: IGNITE-12002
> URL: https://issues.apache.org/jira/browse/IGNITE-12002
> Project: Ignite
> Issue Type: Bug
> Components: cache, general
> Affects Versions: 2.7
> Environment: Running on MacOS 10.12.6
> OpenJDK 11
> Ignite v2.7.0
>
> Reporter: Philippe Anes
> Priority: Major
>
> Create an ignite client (in client mode false) and put some data (10k
> entries/values) to it with very small expiration time (~20s) and TTL enabled.
> Each time the thread is running it'll remove all the entries that expired,
> but after few attempts this thread is not removing all the expired entries,
> some of them are staying in memory and are not removed by this thread
> execution.
> That means we got some expired data in memory, and it's something we want to
> avoid.
> Please can you confirm that is a real issue or just misuse/configuration of
> my test?
> Thanks for your feedback.
>
> To reproduce:
> Git repo: [https://github.com/panes/ignite-sample]
> Run MyIgniteLoadRunnerTest.run() to reproduce the issue described on top.
> (Global setup: Writing 10k entries of 64octets each with TTL 10s)
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
