ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Nettleton (JIRA)" <>
Subject [jira] [Updated] (AMBARI-12532) Blueprint deployment results in some configurations not being resolved properly
Date Fri, 24 Jul 2015 18:21:04 GMT


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

Uploaded initial version of patch

> Blueprint deployment results in some configurations not being resolved properly
> -------------------------------------------------------------------------------
>                 Key: AMBARI-12532
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>            Priority: Critical
>             Fix For: 2.1.1
>         Attachments: AMBARI-12532.patch
> Deployment of a cluster using Blueprints will sometimes fail to properly update all the
configurations on a given cluster prior to attempting the install and start phases for each
> This probably occurs intermittently, and only tends to occur when creating larger clusters,
with 50 or more nodes.  
> This problem can cause a variety of failures, but the most common is that a given configuration
properly on a single host is not updated as expected by the Blueprints processor.  This can
cause service startup failures, such as:
> {code}
> Exception in thread "main" java.lang.IllegalArgumentException: Does not contain a valid
host:port authority: %HOSTGROUP::host_group_1%:8020
> 	at
> 	at
> 	at
> 	at org.apache.hadoop.hdfs.DFSUtil.getAddressesForNameserviceId(
> 	at org.apache.hadoop.hdfs.DFSUtil.getAddressesForNsIds(
> 	at org.apache.hadoop.hdfs.DFSUtil.getAddresses(
> 	at org.apache.hadoop.hdfs.DFSUtil.getHaNnRpcAddresses(
> 	at org.apache.hadoop.hdfs.HAUtil.isHAEnabled(
> 	at
> 	at
> {code}
> The Blueprints processor should wait for all required configuration types that have been
modified to move to the "TOPOLOGY_RESOLVED" state across the cluster before attempting the
first INSTALL task on the cluster. 
> I'm working on a fix for this, and will be submitting a patch shortly. 

This message was sent by Atlassian JIRA

View raw message