You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "John Speidel (JIRA)" <ji...@apache.org> on 2015/05/11 21:39:00 UTC

[jira] [Assigned] (AMBARI-11038) Cluster creation using blueprint is using INITIAL configs

     [ https://issues.apache.org/jira/browse/AMBARI-11038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Speidel reassigned AMBARI-11038:
-------------------------------------

    Assignee: John Speidel  (was: Sumit Mohanty)

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