ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7988) Blueprints export fails to include Yarn Timeline service properties when defaults are used
Date Tue, 28 Oct 2014 01:54:34 GMT

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

Hudson commented on AMBARI-7988:
--------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #726 (See [https://builds.apache.org/job/Ambari-trunk-Commit/726/])
AMBARI-7988.  Ensure that topology related properties with the value of 0.0.0.0 are exported
to blueprint (jspeidel: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f1720123b881b2377fef73bc4f3f7b922c50c64d)
* ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
* ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java


> Blueprints export fails to include Yarn Timeline service properties when defaults are
used
> ------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-7988
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7988
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.7.0
>            Reporter: Robert Nettleton
>            Assignee: Robert Nettleton
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7988.patch, AMBARI-7988_1.7.0.patch
>
>   Original Estimate: 6h
>  Remaining Estimate: 6h
>
> If a Blueprint is exported from a running cluster in Ambari, the following properties
are not included in the exported Blueprint:
> yarn.timeline-service.address,
> yarn.timeline-service.webapp.address,
> yarn.timeline-service.webapp.https.address
> These properties are not included if the stack defaults are not overridden, which is
likely a common case for the Yarn Timeline serivce.  
> If these server properties are overridden with host name information prior to cluster
start, then these properties do appear in the exported blueprint, with the relevant hostname
information removed.
> The problem occurs when the defaults are used with this Yarn service.  The service configuration
defaults to "0.0.0.0", a special IP address used to indicate that a service listens on all
network interfaces on a given machine.  Since this address is slightly different than a normal
host address, it must be handled differently by the Blueprint configuration processor.  
> If the default "0.0.0.0" IP address is used for these defaults in the Yarn Timeline Service,
the Blueprint configuration processor should allow these configuration properties to be included
in the exported Blueprint.  
> The current config processor will remove these properties, since no valid hostname is
found during the export process.  
> 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)

Mime
View raw message