[IGNITE-12002] [TTL] Some expired data remains in memory even with eager TTL enabled

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.7
• Fix Version/s: 2.8
• Component/s: cache, general

Environment

Running on MacOS 10.12.6

OpenJDK 11

Ignite v2.7.0

 

• Ignite Flags: Docs Required
• Assignee: Unassigned
• Reporter: Philippe Anes
• Created: 22/Jul/19 11:34
• Updated: 12/Sep/19 13:44
• Resolved: 12/Sep/19 13:44

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)

Issue Links

• is related to: IGNITE-11438 TTL manager may not clear entries from the underlying CacheDataStore