[
https://issues.apache.org/jira/browse/HBASE-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659789#comment-13659789
]
rajeshbabu commented on HBASE-7006:
-----------------------------------
[~jeffreyz]
Earlier If META assignment failed then we will return from initialization
{code}
- if (!assignMeta(status)) return;
{code}
In side assignMeta
{code}
// Make sure a .META. location is set.
- if (!isMetaLocation()) return false;
- // This guarantees that the transition assigning .META. has completed
-
this.assignmentManager.waitForAssignment(HRegionInfo.FIRST_META_REGIONINFO);
{code}
But now in this patch the logic got changed and even if META not assigned also
initialization getting continued and hanging at .META. migration while locating
meta from zk.
{code}
// Make sure meta assigned before proceeding.
status.setStatus("Assigning Meta Region");
assignMeta(status);
{code}
> [MTTR] Improve Region Server Recovery Time - Distributed Log Replay
> -------------------------------------------------------------------
>
> Key: HBASE-7006
> URL: https://issues.apache.org/jira/browse/HBASE-7006
> Project: HBase
> Issue Type: New Feature
> Components: MTTR
> Reporter: stack
> Assignee: Jeffrey Zhong
> Priority: Critical
> Fix For: 0.98.0, 0.95.1
>
> Attachments: hbase-7006-addendum.patch, hbase-7006-combined.patch,
> hbase-7006-combined-v1.patch, hbase-7006-combined-v4.patch,
> hbase-7006-combined-v5.patch, hbase-7006-combined-v6.patch,
> hbase-7006-combined-v7.patch, hbase-7006-combined-v8.patch,
> hbase-7006-combined-v9.patch, LogSplitting Comparison.pdf,
> ProposaltoimprovelogsplittingprocessregardingtoHBASE-7006-v2.pdf
>
>
> Just saw interesting issue where a cluster went down hard and 30 nodes had
> 1700 WALs to replay. Replay took almost an hour. It looks like it could run
> faster that much of the time is spent zk'ing and nn'ing.
> Putting in 0.96 so it gets a look at least. Can always punt.
--
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
