You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Amitanand Aiyer (Updated) (JIRA)" <ji...@apache.org> on 2012/02/16 20:16:59 UTC
[jira] [Updated] (HBASE-5414) Assign different memstoreTS to
different KV's in the same WALEdit
[ https://issues.apache.org/jira/browse/HBASE-5414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amitanand Aiyer updated HBASE-5414:
-----------------------------------
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.
> Assign different memstoreTS to different KV's in the same WALEdit
> -----------------------------------------------------------------
>
> 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
> Fix For: 0.94.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira