hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeffrey Zhong (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8631) Meta Region First Recovery
Date Wed, 29 May 2013 18:14:20 GMT

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

Jeffrey Zhong commented on HBASE-8631:
--------------------------------------

Could someone else please review the path? The patch solves the issue that recovery sometimes
may get stuck because meta isn't available from integration tests on distributedLogReplay.
Thanks.
                
> 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
>         Attachments: hbase-8631.patch, hbase-8631-v2.patch
>
>
> 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

Mime
View raw message