Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 52F7410229 for ; Fri, 18 Apr 2014 08:12:03 +0000 (UTC) Received: (qmail 41672 invoked by uid 500); 18 Apr 2014 07:45:21 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 41132 invoked by uid 500); 18 Apr 2014 07:45:20 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 40861 invoked by uid 99); 18 Apr 2014 07:45:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Apr 2014 07:45:16 +0000 Date: Fri, 18 Apr 2014 07:45:16 +0000 (UTC) From: "Vinayakumar B (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-10251) Both NameNodes could be in STANDBY State if SNN network is unstable 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/HADOOP-10251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinayakumar B updated HADOOP-10251: ----------------------------------- Attachment: HADOOP-10251.patch Updated the java doc for the interface. Removed the implementation level details in interface. > Both NameNodes could be in STANDBY State if SNN network is unstable > ------------------------------------------------------------------- > > Key: HADOOP-10251 > URL: https://issues.apache.org/jira/browse/HADOOP-10251 > Project: Hadoop Common > Issue Type: Bug > Components: ha > Affects Versions: 2.2.0 > Reporter: Vinayakumar B > Assignee: Vinayakumar B > Priority: Critical > Attachments: HADOOP-10251.patch, HADOOP-10251.patch, HADOOP-10251.patch, HADOOP-10251.patch, HADOOP-10251.patch > > > Following corner scenario happened in one of our cluster. > 1. NN1 was Active and NN2 was Standby > 2. NN2 machine's network was slow > 3. NN1 got shutdown. > 4. NN2 ZKFC got the notification and trying to check for old active for fencing. (This took little more time, again due to slow network) > 5. In between, NN1 got restarted by our automatic monitoring, and ZKFC made it Active. > 6. Now NN2 ZKFC got Old Active as NN1 and it did graceful fencing of NN1 to STANBY. > 7. Before writing ActiveBreadCrumb to ZK, NN2 ZKFC got session timeout and got shutdown before making NN2 Active. > *Now cluster having both NameNodes as STANDBY.* > NN1 ZKFC still thinks that its nameNode is in Active state. > NN2 ZKFC waiting for election. -- This message was sent by Atlassian JIRA (v6.2#6252)