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

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-5414.
----------------------------------------
      Assignee:     (was: Amitanand Aiyer)
    Resolution: Abandoned

> Assign different memstoreTS to different KV's in the same WALEdit during replay
> -------------------------------------------------------------------------------
>
>                 Key: HBASE-5414
>                 URL: https://issues.apache.org/jira/browse/HBASE-5414
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, Coprocessors, regionserver
>            Reporter: Amitanand Aiyer
>            Priority: Major
>         Attachments: ASF.LICENSE.NOT.GRANTED--HBASE-5414.D1749.1.patch
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)