[HBASE-5414] Assign different memstoreTS to different KV's in the same WALEdit during replay

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Abandoned
• Component/s: Client, Coprocessors, regionserver
• Assignee: Unassigned
• Reporter: Amitanand Aiyer
• Created: 16/Feb/12 19:05
• Updated: 12/Jun/22 20:20
• Resolved: 12/Jun/22 20:20

Description

HBASE-5203 combines all the different Puts/Deletes into one WALEdit. This is
required to ensure that we persist the atomic mutation in its enterity and not
in parts.

When combined into a single WALEdit, we create one big familyMap that is a combination
of all the family maps in the mutations. The KV's in this familyMap have no information
about memstoreTS (it is not yet assigned).

However, when we apply the mutations to the Memstore (if there are no failures) we end up
incrementing the memstoreTS for each operation.

This can lead to the client seeing different order of operations – depending on weather or
not there was a RS crash/restart.