[KUDU-218] Should exercise case where a duplicated insert was flushed from neither store

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: M4
• Component/s: tablet, tserver
• Target Version/s: Backlog
• Assignee: Todd Lipcon
• Reporter: Todd Lipcon
• Created: 07/Apr/14 22:48
• Updated: 09/Mar/16 22:31
• Resolved: 09/Mar/16 22:31

Description

David and I were conversing on IRC and thinking about the case where a duplicated update ends up in both the "old" and "new" rowsets of a compaction, but the server crashes before the compaction finishes. In that case, it would show up as "unflushed" in both the before and after targets during bootstrap. I added a FATAL for this case in the bootstrap code and it never triggered, implying that we probably lack test coverage for this important case.

Issue Links

• relates to: KUDU-969 Bootstrap may occasionally mis-identify previously flushed updates