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

Zhihong Yu commented on HBASE-6134:
-----------------------------------

Test failed with NPE at:
{code}
    for (FileStatus fileStatus : listStatus1) {
{code}
Checking for null wouldn't help either:
{code}
Failed tests:   
testSequentialEditLogSeqNum(org.apache.hadoop.hbase.regionserver.wal.TestWALReplay):
 The sequence number of the recoverd.edits and the current edit seq should be 
same expected:<17> but was:<0>
{code}
                
> Improvement for split-worker to speed up distributed-split-log
> --------------------------------------------------------------
>
>                 Key: HBASE-6134
>                 URL: https://issues.apache.org/jira/browse/HBASE-6134
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>             Fix For: 0.96.0
>
>         Attachments: HBASE-6134.patch
>
>
> First,we do the test between local-master-split and distributed split log
> Environment:34 hlog files, 5 regionservers,(after kill one, only 4 rs do ths 
> splitting work)
> local-master-split:60s+
> distributed-split-log:165s+
> In fact, in our production environment, distributed-split-log also took 60s 
> with 30 regionservers for 34 hlog files (regionserver may be in high load)
> We found split-worker split one log file took about 20s.
> I think we should do the improvement for this.

--
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


Reply via email to