Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 28 May 2013 18:50:21 +0000 (UTC)
From: "Himanshu Vashishtha (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12649757.1369766349018.30834.1369767021197@arcas>
In-Reply-To: <JIRA.12649757.1369766349018@arcas>
References: <JIRA.12649757.1369766349018@arcas>
Subject: [jira] [Commented] (HBASE-8631) Meta Region First Recovery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Himanshu Vashishtha commented on HBASE-8631:
--------------------------------------------

I think it is handled in the MetaServerShutdownHandler's process()?
                
> Meta Region First Recovery
> --------------------------
>
>                 Key: HBASE-8631
>                 URL: https://issues.apache.org/jira/browse/HBASE-8631
>             Project: HBase
>          Issue Type: Bug
>          Components: MTTR
>            Reporter: Jeffrey Zhong
>            Assignee: Jeffrey Zhong
>
> We have a separate wal for meta region. While log splitting logic haven't taken the advantage of this and splitlogworker still picks a wal file randomly. Imaging if we have multiple region servers including meta RS fails about the same time while meta wal is recovered last, all failed regions have to wait meta recovered and then can be online again. 
> The open JIRA is to let splitlogworker to pick a meta wal file firstly and then others.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira