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 DA472107EC for ; Wed, 16 Oct 2013 15:47:53 +0000 (UTC) Received: (qmail 26408 invoked by uid 500); 16 Oct 2013 15:47:46 -0000 Delivered-To: apmail-incubator-ambari-dev-archive@incubator.apache.org Received: (qmail 26339 invoked by uid 500); 16 Oct 2013 15:47:45 -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 26133 invoked by uid 99); 16 Oct 2013 15:47:42 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Oct 2013 15:47:42 +0000 Date: Wed, 16 Oct 2013 15:47:42 +0000 (UTC) From: "Aleksandr Kovalenko (JIRA)" To: ambari-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-3526) Reassign Master: HDFS service check fails after Namenode reassignment with HA enabled MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Aleksandr Kovalenko created AMBARI-3526: ------------------------------------------- Summary: Reassign Master: HDFS service check fails after Namenode reassignment with HA enabled Key: AMBARI-3526 URL: https://issues.apache.org/jira/browse/AMBARI-3526 Project: Ambari Issue Type: Task Components: client Affects Versions: 1.4.2 Reporter: Aleksandr Kovalenko Assignee: Aleksandr Kovalenko Priority: Critical Fix For: 1.4.2 We need to make three changes to the wizard. # Step-4 (reassign-step4.png) needs to have first command as Stop NameNode. This command should stop namenode component on the selected source host. This is to makes sure that the selected namenode host to be moved becomes standby before we proceed ahead. # We need to add one more step to the wizard after step-4 (Install, Start and Test). The mockup and purpose of this new step is exactly same as of step7 (Start Components) in namenode HA wizard. Start NameNode command in this step should start active namenode. Active namenode should be on a host which was *not selected* as source host to be moved in the wizard. # There is only one manual command required on manual command page. The message for it should be like: * Login to the newly installed NameNode host * Initialize the metadata by running: {quote} sudo su -l hdfs -c 'hdfs namenode -bootstrapStandby' {quote} * Proceed next -- This message was sent by Atlassian JIRA (v6.1#6144)