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

Ted Yu commented on HBASE-4344:
-------------------------------

This is the error for testRollback based on patch v5:
{code}
testRollback(org.apache.hadoop.hbase.regionserver.TestSplitTransaction)  Time 
elapsed: 1.166 sec  <<< ERROR!
java.lang.ArrayIndexOutOfBoundsException
        at java.lang.System.arraycopy(Native Method)
        at 
org.apache.hadoop.hbase.regionserver.MemStore.maybeCloneWithAllocator(MemStore.java:246)
        at org.apache.hadoop.hbase.regionserver.MemStore.add(MemStore.java:213)
        at org.apache.hadoop.hbase.regionserver.Store.add(Store.java:312)
        at 
org.apache.hadoop.hbase.regionserver.HRegion.applyFamilyMapToMemstore(HRegion.java:2079)
        at org.apache.hadoop.hbase.regionserver.HRegion.put(HRegion.java:2041)
        at org.apache.hadoop.hbase.regionserver.HRegion.put(HRegion.java:1572)
        at org.apache.hadoop.hbase.regionserver.HRegion.put(HRegion.java:1521)
        at 
org.apache.hadoop.hbase.HBaseTestingUtility.loadRegion(HBaseTestingUtility.java:834)
        at 
org.apache.hadoop.hbase.regionserver.TestSplitTransaction.testRollback(TestSplitTransaction.java:213)
{code}

> 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-v2.txt, 4344-v4.txt, 4344-v5.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to