ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Speidel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-11038) Cluster creation using blueprint is using INITIAL configs
Date Mon, 11 May 2015 19:56:02 GMT

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

John Speidel commented on AMBARI-11038:
---------------------------------------

I have a patch up for review now that fully resolves this issue.

> 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)

Mime
View raw message