Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 93E7ACFEB for ; Sat, 26 May 2012 16:05:24 +0000 (UTC) Received: (qmail 80080 invoked by uid 500); 26 May 2012 16:05:24 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 80017 invoked by uid 500); 26 May 2012 16:05:24 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 79890 invoked by uid 99); 26 May 2012 16:05:24 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 16:05:24 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 2443D141822 for ; Sat, 26 May 2012 16:05:24 +0000 (UTC) Date: Sat, 26 May 2012 16:05:24 +0000 (UTC) From: "rajeshbabu (JIRA)" To: issues@hbase.apache.org Message-ID: <183645523.5997.1338048324151.JavaMail.jiratomcat@issues-vm> In-Reply-To: <1911362584.16490.1335950570941.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Updated] (HBASE-5916) RS restart just before master intialization we make the cluster non operative MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-5916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rajeshbabu updated HBASE-5916: ------------------------------ Status: Patch Available (was: Open) > RS restart just before master intialization we make the cluster non operative > ----------------------------------------------------------------------------- > > Key: HBASE-5916 > URL: https://issues.apache.org/jira/browse/HBASE-5916 > Project: HBase > Issue Type: Bug > Affects Versions: 0.94.0, 0.92.1 > Reporter: ramkrishna.s.vasudevan > Assignee: ramkrishna.s.vasudevan > Priority: Critical > Fix For: 0.94.1 > > Attachments: HBASE-5916_trunk.patch, HBASE-5916_trunk_1.patch, HBASE-5916_trunk_1.patch, HBASE-5916_trunk_2.patch, HBASE-5916_trunk_3.patch, HBASE-5916_trunk_4.patch, HBASE-5916_trunk_v5.patch, HBASE-5916_trunk_v6.patch, HBASE-5916_trunk_v7.patch, HBASE-5916_trunk_v8.patch, HBASE-5916v8.patch > > > Consider a case where my master is getting restarted. RS that was alive when the master restart started, gets restarted before the master initializes the ServerShutDownHandler. > {code} > serverShutdownHandlerEnabled = true; > {code} > In this case when the RS tries to register with the master, the master will try to expire the server but the server cannot be expired as still the serverShutdownHandler is not enabled. > This case may happen when i have only one RS gets restarted or all the RS gets restarted at the same time.(before assignRootandMeta). > {code} > LOG.info(message); > if (existingServer.getStartcode() < serverName.getStartcode()) { > LOG.info("Triggering server recovery; existingServer " + > existingServer + " looks stale, new server:" + serverName); > expireServer(existingServer); > } > {code} > If another RS is brought up then the cluster comes back to normalcy. > May be a very corner case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira