Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 6 Sep 2013 22:40:52 +0000 (UTC)
From: "Jimmy Xiang (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12667404.1378505955926.94849.1378507252029@arcas>
In-Reply-To: <JIRA.12667404.1378505955926@arcas>
References: <JIRA.12667404.1378505955926@arcas>
Subject: [jira] [Commented] (HBASE-9456) Meta doesn't get assigned in a
 master failure scenario
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-9456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13760711#comment-13760711 ] 

Jimmy Xiang commented on HBASE-9456:
------------------------------------

I see why. SSH used to be enabled quickly.  Now, due to the system table assignment, it's enable is delayed.  Let me think through the issue and come up a cleaner fix.
                
> Meta doesn't get assigned in a master failure scenario
> ------------------------------------------------------
>
>                 Key: HBASE-9456
>                 URL: https://issues.apache.org/jira/browse/HBASE-9456
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Devaraj Das
>             Fix For: 0.96.0
>
>         Attachments: 9456-1.txt
>
>
> The flow:
> 1. Cluster is up, meta is assigned to some server
> 2. Master is killed
> 3. Master is brought up, it is initializing. It learns about the Meta server (in assignMeta).
> 4. Server holding meta is killed
> 5. Meta never gets reassigned since the SSH wasn't enabled

--
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