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

Hadoop QA commented on HBASE-10000:
-----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12618190/10000-recover-ts-with-pb-8.txt
  against trunk revision .
  ATTACHMENT ID: 12618190

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 25 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/10768//console

This message is automatically generated.

> Initiate lease recovery for outstanding WAL files at the very beginning of 
> recovery
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-10000
>                 URL: https://issues.apache.org/jira/browse/HBASE-10000
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>             Fix For: 2.0.0
>
>         Attachments: 10000-0.96-v5.txt, 10000-0.96-v6.txt, 
> 10000-recover-ts-with-pb-2.txt, 10000-recover-ts-with-pb-3.txt, 
> 10000-recover-ts-with-pb-4.txt, 10000-recover-ts-with-pb-5.txt, 
> 10000-recover-ts-with-pb-6.txt, 10000-recover-ts-with-pb-7.txt, 
> 10000-recover-ts-with-pb-8.txt, 10000-recover-ts-with-pb-8.txt, 10000-v4.txt, 
> 10000-v5.txt, 10000-v6.txt
>
>
> At the beginning of recovery, master can send lease recovery requests 
> concurrently for outstanding WAL files using a thread pool.
> Each split worker would first check whether the WAL file it processes is 
> closed.
> Thanks to Nicolas Liochon and Jeffery discussion with whom gave rise to this 
> idea. 



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

Reply via email to