?That seems odd. If, after config changes, the affected services/components are restarted then the command also refreshes client configs. You should see "install" commands for all client components in the command history.
In any case, its not related to the auto start feature. Try it again and see if the restart operation for all components affected by config change do not include re-install of the client components. That is an issue to investigate. -Sumit ________________________________ From: Latha Appanna <[email protected]> Sent: Friday, September 1, 2017 11:02 AM To: [email protected] Subject: Re: Clients components(Refreshing config) are not restarted on all hosts with ambari auto recovery Hi Sumit, The configurations changes done even before VM is rebooted ( and all affected components were also re-started after configuration changes) are not refreshed on all hosts(that has the required CLIENT) in our case. Is this behavior expected? Thanks & Regards, Latha On Fri, Sep 1, 2017 at 6:09 PM, Sumit Mohanty <[email protected]<mailto:[email protected]>> wrote: As clients are only INSTALLED and not STARTED, auto start skips the clients. Even with auto start enabled, if configs are being changed then "refresh/restart" operation should be performed explicitly using UI or API. Auto start is mostly for recovery when VM is rebooted or process dies for some reason. -Sumit ________________________________ From: Latha Appanna <[email protected]<mailto:[email protected]>> Sent: Friday, September 1, 2017 4:28 AM To: [email protected]<mailto:[email protected]> Subject: Clients components(Refreshing config) are not restarted on all hosts with ambari auto recovery Hello, In our clusters, we have noticed that client components of all services are not restarted (i.e configuration are not refreshed) in auto recovery mode. Even though all the components are enabled for recovery. Thanks & Regards, Latha
