[ https://issues.apache.org/jira/browse/AMBARI-24919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated AMBARI-24919: ------------------------------------ Labels: pull-request-available (was: ) > Allow Namenode HA setup with external namenodes in > BlueprintConfigurationProcessor > ---------------------------------------------------------------------------------- > > Key: AMBARI-24919 > URL: https://issues.apache.org/jira/browse/AMBARI-24919 > Project: Ambari > Issue Type: Task > Affects Versions: 2.7.2 > Reporter: Balázs Bence Sári > Assignee: Balázs Bence Sári > Priority: Critical > Labels: pull-request-available > Fix For: trunk > > > There is an increasing demand for clusters with some of the components being > managed externally to Ambari. > This ticket addresses the problem where the cluster contains a HDFS_CLIENT > but server HDFS server components are external and NAMENODE is HA. > In this cases, cluster template validation failed as there were 0 name nodes > which is less than the expected minimum of two. > Going forward the following setup should pass validation: > - Namenode HA is enabled > - There are 0 namenodes > - all namenode dfs rpc addresses point to an external fqdn. > This will give sufficent protection against accidentally omitted namenodes, > however will enable clusters with external namenodes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)