[jira] [Commented] (AMBARI-6471) Add Services Wizard can corrupt config files unpredictably

["Srimanth Gunturi (JIRA)" <ji...@apache.org>]

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

Srimanth Gunturi commented on AMBARI-6471:
------------------------------------------

Review at https://reviews.apache.org/r/23441/

> Add Services Wizard can corrupt config files unpredictably
> ----------------------------------------------------------
>
>                 Key: AMBARI-6471
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6471
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.1
>            Reporter: Srimanth Gunturi
>            Assignee: Srimanth Gunturi
>            Priority: Blocker
>             Fix For: 1.6.1
>
>
> Testing using the 1.6.1 RC bits (branch-1.6.1, hash=ffb702b252a8b979529864ec5579465a122060b5) revealed that Add Services can corrupt config files in an unpredictable manner.
> We have seen:
> * adding Pig resulted in core-site dropping all existing properties except for "hadoop.proxyuser.falcon.hosts and hadoop.proxyuser.falcon.groups"
> * add Storm resulted in core-site retaining all existing properties but dropping hadoop.proxyuser.* settings for all services except Falcon
> * adding Storm dropped a number of existing properties in yarn-site (and NodeManagers can no longer restart after that)
> The bottomline here is that behavior seems pretty random (adding the same service on different clusters results in different behavior).
> Also, when adding a service, certain configs (like hdfs-site) were not cloned while most other configs (like yarn-site, mapred-site) get cloned even if no property changes are made regardless of which service is added.
> Update: changes to hdfs-site during Add Services Wizard never persists.



--
This message was sent by Atlassian JIRA
(v6.2#6252)