You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2013/04/03 17:59:17 UTC

[jira] [Created] (AMBARI-1774) Ambari does not push the config updates to the client/gateway node

Siddharth Wagle created AMBARI-1774:
---------------------------------------

             Summary: 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


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