[
https://issues.apache.org/jira/browse/AMBARI-11038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539027#comment-14539027
]
Hudson commented on AMBARI-11038:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #2565 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2565/])
AMBARI-11038. Fix timing issue regarding setting of topology resolved
configuration (jspeidel:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=66a4bfb26ad5ffffa59d925e56f465bec3346696)
*
ambari-server/src/main/java/org/apache/ambari/server/topology/ClusterConfigurationRequest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/LogicalRequest.java
*
ambari-server/src/test/java/org/apache/ambari/server/topology/TopologyManagerTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/topology/TopologyManager.java
> Cluster creation using blueprint is using INITIAL configs
> ---------------------------------------------------------
>
> Key: AMBARI-11038
> URL: https://issues.apache.org/jira/browse/AMBARI-11038
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Sumit Mohanty
> Assignee: John Speidel
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-11038.patch
>
>
> When cluster is deployed using blueprints, an INITIAL set of configs are
> created that are resolved to create TOPOLOGY_RESOLVED configurations. It
> looks like the INITIAL set of configs are being used for the first set of
> tasks created for cluster install. The INITIAL configs are not usually
> accurate as it does not have resolved host names. Also some configs such as
> memory settings are not resolved to use correct format or tag.
> The approach to fix is to ensure that TOPOLOGY_RESOLVED configs are created
> before any command is executed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
