[
https://issues.apache.org/jira/browse/HBASE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12835870#action_12835870
]
stack commented on HBASE-2235:
------------------------------
@Kannan Do I have test-13 regionserver log? Is that the one that crashed/GC
paused (I have that one). I'm asking because test1,249509,1266107874886 was
the parent whose daughters were not online after you did your restart. I'd
like to see its log to see how come the parent offlining worked but not the
daughter additions especially if you had hdfs-200 in place.
> Mechanism that would not have -ROOT- and .META. on same server caused failed
> assign of .META.
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-2235
> URL: https://issues.apache.org/jira/browse/HBASE-2235
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.4, 0.21.0
>
>
> Here is the short story:
> Scenario is a cluster of 3 servers. Server 1. crashed. It was carrying the
> .META. We split the logs. .META. is put on the head of the assignment
> queue. Server 2. happens to be in a state where it wants to report a split.
> The master fails the report because there is no .META. (It fails it ugly with
> a NPE). Server 3. checks in and falls into the assignment code
> (RegionManager#regionsAwaitingAssignment). In here we have this bit of code
> around line #412:
> {code}
> if (reassigningMetas && isMetaOrRoot && !isSingleServer) {
> return regionsToAssign; // dont assign anything to this server.
> }
> {code}
> Because we think this not a single server cluster -- we think there are two
> 'live' nodes -- we won't assign meta.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
