Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 22 Feb 2016 09:10:18 +0000 (UTC)
From: "secfree (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12940989.1456132204000.107678.1456132218130@Atlassian.JIRA>
In-Reply-To: <JIRA.12940989.1456132204000@Atlassian.JIRA>
References: <JIRA.12940989.1456132204000@Atlassian.JIRA>
 <JIRA.12940989.1456132204717@arcas>
Subject: [jira] [Created] (AMBARI-15126) Update wrong namenode config when
 moving namenode
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

secfree created AMBARI-15126:
--------------------------------

             Summary: Update wrong namenode config when moving namenode
                 Key: AMBARI-15126
                 URL: https://issues.apache.org/jira/browse/AMBARI-15126
             Project: Ambari
          Issue Type: Bug
          Components: ambari-web
    Affects Versions: 2.1.2
            Reporter: secfree
            Priority: Critical


Condition:
1. hdfs deploy ha
2. "dfs.namenode.http-address" is not set to the default port 50070

Result:
1. Ambari will always substitute configures relative to "nn2"
2. The active "Move Namenode" failed and make configure inconsistent, the cluster crashes

Code location
{code:title=ambari-web/app/controllers/main/service/reassign/step4_controller.js|borderStyle=solid}

if (App.get('isHaEnabled')) {
      var nameServices = configs['hdfs-site']['dfs.nameservices'];
      var suffix = (configs['hdfs-site']['dfs.namenode.http-address.' + nameServices + '.nn1'] === sourceHostName + ':50070') ? '.nn1' : '.nn2';
      configs['hdfs-site']['dfs.namenode.http-address.' + nameServices + suffix] = targetHostName + ':50070';
      ...
    }
{code}


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)