[ 
https://issues.apache.org/jira/browse/AMBARI-10487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14503218#comment-14503218
 ] 

Hadoop QA commented on AMBARI-10487:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12726577/AMBARI-10487.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 1 new 
or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2423//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2423//console

This message is automatically generated.

> Blueprint processor fails to handle direct host names properly in HA 
> Blueprints
> -------------------------------------------------------------------------------
>
>                 Key: AMBARI-10487
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10487
>             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.0
>
>         Attachments: AMBARI-10487.patch, 
> exported_ha_blueprint_with_manual_updates_direct_host_names.json, 
> ha_cluster_creation_template.json
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> The Blueprint Configuration processor is not handling certain HA-specific 
> properties (HDFS HA for one example) when host names are specified directly.
> If a customer wishes to specify hostnames directly in the HDFS HA properties 
> that require hostnames, the Blueprint processor will fail if it detects more 
> than one NameNode (which is the case in an HA cluster) and does not find the 
> %HOSTGROUP% syntax to use for hostname substitution.
> The Blueprint config processor should be updated, so that customer-supplied 
> hostnames in these properties are used, and the Blueprint processor should 
> function properly with hostnames supplied directly.
> This fix should also be applied and tested across the other types of HA in 
> Blueprints, and care should be taken to ensure that a customer can supply 
> hostnames directly, or can use the %HOSTGROUP% syntax, or a combination of 
> the two approaches.



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

Reply via email to