ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Olivér Szabó (JIRA) <j...@apache.org>
Subject [jira] [Updated] (AMBARI-13099) Host group level config changes are not picked up with Blueprint provisioning
Date Tue, 15 Sep 2015 11:05:46 GMT

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

Olivér Szabó updated AMBARI-13099:
----------------------------------
    Attachment: AMBARI-13099.patch

> Host group level config changes are not picked up with Blueprint provisioning
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-13099
>                 URL: https://issues.apache.org/jira/browse/AMBARI-13099
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.1
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>            Priority: Blocker
>             Fix For: 2.1.2
>
>         Attachments: AMBARI-13099.patch
>
>
> Installing a cluster with a blueprint that contains host group level configurations are
not picked up during install time. Ambari UI complains to restart few services after installation
which doesn't make sense.
> In the provided BP there are host group level config like: 
> {
> "hdfs-site" :
> { "dfs.datanode.data.dir" : "/hadoopfs/fs1/hdfs/datanode,/hadoopfs/fs2/hdfs/datanode"
}
> },
> {
> "yarn-site" :
> { "yarn.nodemanager.local-dirs" : "/hadoopfs/fs1/yarn/nodemanager,/hadoopfs/fs2/yarn/nodemanager",
"yarn.nodemanager.log-dirs" : "/hadoopfs/fs1/yarn/nodemanager/log,/hadoopfs/fs2/yarn/nodemanager/log"
}
> }
> and those directories are not in use, but the default ones.



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

Mime
View raw message