Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 4 Jun 2015 20:04:38 +0000 (UTC)
From: "Robert Nettleton (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12835511.1433447998000.15367.1433448278534@Atlassian.JIRA>
In-Reply-To: <JIRA.12835511.1433447998000@Atlassian.JIRA>
References: <JIRA.12835511.1433447998000@Atlassian.JIRA>
 <JIRA.12835511.1433447998774@arcas>
Subject: [jira] [Updated] (AMBARI-11701) Blueprint should not require
 single-node properties for NameNodes in an HDFS NameNode HA cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-11701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Nettleton updated AMBARI-11701:
--------------------------------------
    Attachment: AMBARI-11701.patch

Uploaded initial version of patch.

> Blueprint should not require single-node properties for NameNodes in an HDFS NameNode HA cluster
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-11701
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11701
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.0.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-11701.patch
>
>
> The Blueprints processor currently will fail during the deployment of an HDFS NameNode HA cluster if the following properties in "hdfs-site" are not specified in the Blueprint:
> "dfs.namenode.http-address"
> "dfs.namenode.https-address"
> "dfs.namenode.rpc-address"
> These HDFS address properties are required in a non-HA scenario, but should not be required when an HA cluster is configured.  In the HA configuration, there are settings for each of these address properties on a per-namenode basis (with the property names including the name of the nameservice and namenode). 
> The Blueprint processor will currently fail to start a cluster, and throw an error back to the cluster deployer, mentioning that these properties must be set.  This is incorrect, since HDFS does not require these properties in an HA cluster. 
> I'm working on a fix for this, and will be submitting a patch shortly. 


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