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-11959) Remove Tez UI property from exported Blueprint
Date Wed, 17 Jun 2015 01:31:03 GMT

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

Hudson commented on AMBARI-11959:
---------------------------------

SUCCESS: Integrated in Ambari-trunk-Commit #2940 (See [https://builds.apache.org/job/Ambari-trunk-Commit/2940/])
AMBARI-11959. Remove Tez UI property from exported Blueprint. (rnettleton) (rnettleton: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=ac508b8dffb923b717bf66572b0bc14ba9f2ff3f)
* 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


> Remove Tez UI property from exported Blueprint
> ----------------------------------------------
>
>                 Key: AMBARI-11959
>                 URL: https://issues.apache.org/jira/browse/AMBARI-11959
>             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-11959.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Recent changes in the StackAdvisor code have caused the following Tez property to be
added to a cluster's configuration:
> "tez.tez-ui.history-url.base" in "tez-site"
> This property is used to connect the Yarn ResourceManager UI to the Tez UI located in
the Tez View.  The UI's stack advisor will set this property automatically. 
> This property now appears in Blueprint exports of running clusters, and the property
value includes hostname information.  This makes the exported Blueprint less portable, since
it will require some manual changes to this property on a different set of machines.  
> This property cannot be handled by the current Blueprint config processor, since the
URL required by this property involves information about deployed Tez View, which is not readily
accessible to the Blueprints processor.
> The Blueprint configuration processor should filter out this property during a Blueprint
export.  



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

Mime
View raw message