[OAK-8033] Node states sometimes refer to more than a single generation of segments after a full compaction

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.8.10, 1.6.16, 1.8.11
• Fix Version/s: 1.12.0, 1.6.17, 1.10.1, 1.8.12
• Component/s: segment-tar
• Labels: TarMK
• Assignee: Michael Dürig
• Reporter: Michael Dürig
• Created: 07/Feb/19 16:09
• Updated: 12/Jul/19 13:49
• Resolved: 18/Feb/19 16:20

Description

Due to a regression introduced with OAK-7867 a full compaction can sometimes cause nodes that are written concurrently to reference segments from more than a single gc generation.

This happens when the borrowWriter method needs to create a new writer. In this case the new writer will be of the generation of the current head state instead of the generation associated with the current write operation in progress.

 

cc frm, ahanikel

 

Issue Links

• is duplicated by: OAK-8039 Intermittent test failure of CompactionAndCleanupIT.testMixedSegments
• is related to: OAK-7867 Flush thread gets stuck when input stream of binaries block
• is related to: OAK-7908 Backport and validate OAK-7867 to Oak 1.8
• is related to: OAK-7909 Backport and validate OAK-7867 to Oak 1.6
• relates to: OAK-8039 Intermittent test failure of CompactionAndCleanupIT.testMixedSegments