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 (JIRA)" <ji...@apache.org> on 2011/09/07 20:33:09 UTC

[jira] [Updated] (HBASE-4344) Persist memstoreTS to disk

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

Amitanand Aiyer updated HBASE-4344:
-----------------------------------

    Fix Version/s:     (was: 0.94.0)
                   0.89.20100924
         Assignee: Amitanand Aiyer
           Status: Patch Available  (was: Open)

> Persist memstoreTS to disk
> --------------------------
>
>                 Key: HBASE-4344
>                 URL: https://issues.apache.org/jira/browse/HBASE-4344
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Amitanand Aiyer
>            Assignee: Amitanand Aiyer
>             Fix For: 0.89.20100924
>
>
> Atomicity can be achieved in two ways -- (i) by using  a multiversion concurrency system (MVCC), or (ii) by ensuring that "new" writes do not complete, until the "old" reads complete.
> Currently, Memstore uses something along the lines of MVCC (called RWCC for read-write-consistency-control). But, this mechanism is not incorporated for the key-values written to the disk, as they do not include the memstore TS.
> Let us make the two approaches be similar, by persisting the memstoreTS along with the key-value when it is written to the disk.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira