-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51597/
-----------------------------------------------------------
(Updated Sept. 2, 2016, 12:08 p.m.)
Review request for Ambari, Jonathan Hurley, Sandor Magyari, and Sebastian
Toader.
Bugs: AMBARI-18302
https://issues.apache.org/jira/browse/AMBARI-18302
Repository: ambari
Description
-------
Configuration changes are propagated to host components by issuing a restart of
the affected components.
In case of master components this action will start the affected components
(regardless it is in INSTALLED or STARTED state) and the desired state will be
set to STARTED.
In Ambari client components are always expected to be in INSTALLED state.
However upon configuration changes, the desired state of these components are
also set to STARTED. This may be misleading for ambari API users that determine
component states by checking the desired state and actual state. (The actual
state in case of client components will always be INSTALLED)
This issue addresses this problem by not updating the desired state when client
components are restarted.
Diffs (updated)
-----
ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java
8c8ae10
Diff: https://reviews.apache.org/r/51597/diff/
Testing
-------
Unit tests running.
Thanks,
Laszlo Puskas
