hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4344) Persist memstoreTS to disk
Date Wed, 14 Sep 2011 01:16:09 GMT

    [ https://issues.apache.org/jira/browse/HBASE-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104136#comment-13104136
] 

stack commented on HBASE-4344:
------------------------------

@Amit you want to revise your patch?  We're trying to branch 0.92 this friday.  Would be nice
to include this fix.

> 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
>
>         Attachments: patch-2
>
>
> 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

        

Mime
View raw message