[ https://issues.apache.org/jira/browse/HBASE-4344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amitanand Aiyer updated HBASE-4344: ----------------------------------- Attachment: 4344-v12.txt combine 4344-v11.txt with 4485-v4.txt Running the testsuite (in progress) > 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