[ https://issues.apache.org/jira/browse/AMBARI-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Wagle updated AMBARI-1774:
------------------------------------
Attachment: AMBARI-1774-3.patch
Incorporated comments.
> Ambari does not push the config updates to the client/gateway node
> ------------------------------------------------------------------
>
> Key: AMBARI-1774
> URL: https://issues.apache.org/jira/browse/AMBARI-1774
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.3.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 1.3.0
>
> Attachments: AMBARI-1774-2.patch, AMBARI-1774-3.patch, AMBARI-1774.patch
>
>
> What happens is this, lets say you pick a
> host as a gateway which has no service daemons running.
> If you make the config changes, they can only be deployed to daemon
> nodes currently and cant be deployed to client nodes as of now. This
> is a bug in Ambari since you will never be able to update the client
> configs on a gateway node since the server will never push it to a
> client node (since no start/stop is happening on that node).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|