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

stack updated HBASE-12782:
--------------------------
    Attachment: 12782.search.plus.archive.recovered.edits.txt

Patch that adds means of archiving recovered.edits files rather than delete 
them (does it by faking out the archiving mechanism that 'recovered.edits' is a 
column family name).

Did a new run with the flag to keep recovered.edits in archive.  Looking at the 
first incidence of loss, the missing edits are present in the recovered.edits 
file.  We are dropping them on replay somehow.

Will be back.

> ITBLL fails for me if generator does anything but 5M per maptask
> ----------------------------------------------------------------
>
>                 Key: HBASE-12782
>                 URL: https://issues.apache.org/jira/browse/HBASE-12782
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>    Affects Versions: 1.0.0
>            Reporter: stack
>            Priority: Critical
>             Fix For: 1.0.1
>
>         Attachments: 12782.search.plus.archive.recovered.edits.txt, 
> 12782.search.plus.txt, 12782.search.txt, 12782.unit.test.and.it.test.txt, 
> 12782.unit.test.writing.txt
>
>
> Anyone else seeing this?  If I do an ITBLL with generator doing 5M rows per 
> maptask, all is good -- verify passes. I've been running 5 servers and had 
> one splot per server.  So below works:
> HADOOP_CLASSPATH="/home/stack/conf_hbase:`/home/stack/hbase/bin/hbase 
> classpath`" ./hadoop/bin/hadoop --config ~/conf_hadoop 
> org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList --monkey 
> serverKilling Generator 5 5000000 g1.tmp
> or if I double the map tasks, it works:
> HADOOP_CLASSPATH="/home/stack/conf_hbase:`/home/stack/hbase/bin/hbase 
> classpath`" ./hadoop/bin/hadoop --config ~/conf_hadoop 
> org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList --monkey 
> serverKilling Generator 10 5000000 g2.tmp
> ...but if I change the 5M to 50M or 25M, Verify fails.
> Looking into it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to