[
https://issues.apache.org/jira/browse/HBASE-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13669784#comment-13669784
]
Devaraj Das commented on HBASE-8631:
------------------------------------
Some comments:
1. Are the timeout related changes in HLogSplitter relevant to this issue?
2. _if ("filter != null && filter == MasterFileSystem.META_FILTER "_ -> No need
for a null check?
3. removeRecoveringRegionsFromZK now has a new argument called carryingMeta.
The name of the argument should be changed to better reflect the usage.
4. See if you can add unit tests for the issues.
> 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
