You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/09/01 07:30:55 UTC
[jira] Resolved: (HBASE-2235) Mechanism that would not have -ROOT-
and .META. on same server caused failed assign of .META.
[ https://issues.apache.org/jira/browse/HBASE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-2235.
--------------------------
Resolution: Invalid
Not possible under HBASE-2692. New LoadBalancer does not have special rules that would have .META. and -ROOT- on separate servers.
> 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: HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.90.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.