Return-Path: X-Original-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ambari-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B30E8108CB for ; Sat, 28 Sep 2013 01:01:58 +0000 (UTC) Received: (qmail 9829 invoked by uid 500); 28 Sep 2013 01:01:58 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 9802 invoked by uid 500); 28 Sep 2013 01:01:58 -0000 Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ambari-dev@incubator.apache.org Delivered-To: mailing list ambari-dev@incubator.apache.org Received: (qmail 9794 invoked by uid 99); 28 Sep 2013 01:01:58 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 28 Sep 2013 01:01:58 +0000 Date: Sat, 28 Sep 2013 01:01:58 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-3368) NameNode start hangs with HA config'd 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/AMBARI-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated AMBARI-3368: ------------------------------------ Attachment: AMBARI-3368-1.patch > NameNode start hangs with HA config'd > ------------------------------------- > > Key: AMBARI-3368 > URL: https://issues.apache.org/jira/browse/AMBARI-3368 > Project: Ambari > Issue Type: Bug > Components: agent > Affects Versions: 1.4.1 > Reporter: Siddharth Wagle > Assignee: Siddharth Wagle > Fix For: 1.4.1 > > Attachments: AMBARI-3368-1.patch, AMBARI-3368.patch > > > After configuring NameNode HA, I found starting a namenode hangs and fails with "Puppet has been killed due to timeout" > 1) Install cluster > 2) enable NameNode HA > 3) Stop standby namenode on Hosts details page > 4) Stop active namenode on Hosts details page > 5) Start namenode on Hosts details page > 6) Hangs on start. stops at 35% complete. Then after ~ 10 minutes, puppet has been killed due to timeout -- 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