Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sat, 5 Mar 2011 06:18:45 +0000 (UTC)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <592291840.697.1299305925851.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <19271703.10501291066211151.JavaMail.jira@thor>
Subject: [jira] Commented: (HBASE-3285) Hlog recovery takes too much time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-3285:
------------------------------

Did a bit of server killing on a cluster that was up on the tip of branch-0.20-append -- i.e. had hdfs-1520, 1555, and 1554 -- and recovery of lease seems to run nice and promptly.  Testing now on the branch-0.20-append that hbase 0.90.1 ships with, a branch-0.20-append that was absent 1520, 1555, and 1554.

> Hlog recovery takes too much time
> ---------------------------------
>
>                 Key: HBASE-3285
>                 URL: https://issues.apache.org/jira/browse/HBASE-3285
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Hairong Kuang
>            Assignee: Hairong Kuang
>         Attachments: 3285-v2.txt, hbaseRecoverHLog.patch
>
>
> Currently HBase uses append to trigger the close of HLog during Hlog split. Append is a very expensive operation, which involves not only NameNode operations but creating a writing pipeline. If one of datanodes on the pipeline has a problem, this recovery may takes minutes. I'd like implement a lightweight NameNode operation to trigger lease recovery and make HBase to use this instead.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira