[IGNITE-21125] Prevent duplicate keys in dump

• Type: Task
• Status: Patch Available
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: 2.17
• Labels: IEP-109 ise pull-request-available
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Nikolay Izhikov
• Reporter: Nikolay Izhikov
• Created: 19/Dec/23 20:58
• Updated: 20/Dec/23 19:11

Description

Currently, cache dump can contain the same key several times.
In the read time we must maintain Set of read keys to filter out duplicates.
So dump read leads to high GC pressure.

We can overcome this issue and filter out duplicates in the write time:

• Iterator don't write keys that was written by beforeChange listener, already.

• Partition Iterator returns key in ascending order. Order set by CacheDataTree#compare method.
• beforeChange listener must not write keys that was already written by the iterator.

Cheap algorithm is the following:

• Store last key written by iterator.
• If changed key (in beforeChange) less then last key written by iterator then it must be skiped. Because, it already saved by the iterator.

Issue Links

• links to: GitHub Pull Request #11112