hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Created: (HBASE-2235) Mechanism that would not have -ROOT- and .META. on same server caused failed assign of .META.
Date Thu, 18 Feb 2010 04:59:28 GMT
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.


Mime
View raw message