hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4344) Persist memstoreTS to disk
Date Wed, 02 Nov 2011 00:45:33 GMT

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

Nicolas Spiegelberg commented on HBASE-4344:

What is the problem holding v12 from commit?  I think we can check in this JIRA and wait to
commit HBASE-4485 until the deadlock issue is solved.  In general, can we get as many of the
HBASE-2856 JIRAs committed while not introducing any regression?  I don't think we need to
solve the HBASE-2856 issue completely until we can commit anything.  Forward progress without
steps back is sufficient.  Having this large array of uncommitted patch files is very unwieldy
for patch management.
> 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: 4344-v10.txt, 4344-v11.txt, 4344-v12.txt, 4344-v2.txt, 4344-v4.txt,
4344-v5.txt, 4344-v6.txt, 4344-v7.txt, 4344-v8.txt, 4344-v9.txt, 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.
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


View raw message