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 8BBD7102FC for ; Wed, 31 Jul 2013 00:31:50 +0000 (UTC) Received: (qmail 60295 invoked by uid 500); 31 Jul 2013 00:31:49 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 60261 invoked by uid 500); 31 Jul 2013 00:31:49 -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 60175 invoked by uid 99); 31 Jul 2013 00:31:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Jul 2013 00:31:49 +0000 Date: Wed, 31 Jul 2013 00:31:49 +0000 (UTC) From: "Siddharth Wagle (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-2775) Ability to add second Namenode to the cluster for 2.0.* stack MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Siddharth Wagle created AMBARI-2775: --------------------------------------- Summary: Ability to add second Namenode to the cluster for 2.0.* stack Key: AMBARI-2775 URL: https://issues.apache.org/jira/browse/AMBARI-2775 Project: Ambari Issue Type: Bug Components: agent Affects Versions: 1.3.0 Reporter: Siddharth Wagle Assignee: Siddharth Wagle Fix For: 1.3.0 Verifying that installing and starting namenode using current Ambari scripts does not reformat the NN 2. This is because the bootstrap namenode should have formatted the namenode 2 already. Also fix tests affected by NN HA changes. -- 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