ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <>
Subject [jira] [Commented] (AMBARI-1774) Ambari does not push the config updates to the client/gateway node
Date Wed, 03 Apr 2013 19:51:15 GMT


Sumit Mohanty commented on AMBARI-1774:

* ambari-server/src/main/java/org/apache/ambari/server/controller/
** addClientSchForReinstall: If there are no service that are being started can we not return
immediately? Do we need to identify hosts if services are being STOPPED/INSTALLED?
** When we are populating existing SCHs then it seems that we are not ensuring uniqueness.
the same host could be listed multiple times for different service components. This host will
get added multiple times. (it may or may not be an issue though)
** Line 1883: Missing curly braces
** Line 1893: They are not potential anymore. Can we modify the log?
* ambari-server/src/test/java/org/apache/ambari/server/controller/
** Line 4432: Modify the comment to stopped as the state is being changed to INSTALLED
** We should add a MAPREDUCE_CLIENT to the host that has DATANODE to simulate the scenario
where we send INSTALLED to a host even if it has a SLAVE/MASTER component. This is a good
scenario to add coverage to.
> Ambari does not push the config updates to the client/gateway node
> ------------------------------------------------------------------
>                 Key: AMBARI-1774
>                 URL:
>             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.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:

View raw message