[OAK-6519] Properly handle tail compactions in deduplication caches

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.6, 1.8.0
• Component/s: segment-tar
• Labels: compaction gc
• Epic Link: TarMK GC scalability
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 04/Aug/17 08:20
• Updated: 25/Aug/17 04:30
• Resolved: 07/Aug/17 13:59

Description

This is a follow up to OAK-3349, which introduced tail compactions:

The deduplication caches currently only take the full generations into account and ignore the tail generations. Cache generations need to be a monotonically increasing, ordered sequence consisting of the full and tail part of the gc generation. See FileStoreBuilder.EvictingWriteCacheManager.evictOldGeneration. Optimally we find a way to decouple the segment generation from the cache generations as these are really separate concerns.

Issue Links

• is related to: OAK-3349 Partial compaction