[HBASE-8721] Deletes can mask puts that happen after the delete

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Component/s: regionserver
• Assignee: Unassigned
• Reporter: Honghua Feng
• Created: 09/Jun/13 09:54
• Updated: 16/Jun/22 17:08
• Resolved: 20/Jun/13 18:44

Description

this fix aims for bug mentioned in http://hbase.apache.org/book.html 5.8.2.1:

"Deletes mask puts, even puts that happened after the delete was entered. Remember that a delete writes a tombstone, which only disappears after then next major compaction has run. Suppose you do a delete of everything <= T. After this you do a new put with a timestamp <= T. This put, even if it happened after the delete, will be masked by the delete tombstone. Performing the put will not fail, but when you do a get you will notice the put did have no effect. It will start working again after the major compaction has run. These issues should not be a problem if you use always-increasing versions for new puts to a row. But they can occur even if you do not care about time: just do delete and put immediately after each other, and there is some chance they happen within the same millisecond."

Issue Links

• relates to: HBASE-8770 deletes and puts with the same ts should be resolved according to mvcc/seqNum