[
https://issues.apache.org/jira/browse/AMBARI-18302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Toader updated AMBARI-18302:
--------------------------------------
Fix Version/s: (was: trunk)
2.5.0
> Desired state of client component should not be changed in case configuration
> changes are applied through a "Restart"
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-18302
> URL: https://issues.apache.org/jira/browse/AMBARI-18302
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Laszlo Puskas
> Assignee: Laszlo Puskas
> Fix For: 2.5.0
>
> Attachments: AMBARI-18302.trunk.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
