[ https://issues.apache.org/jira/browse/AMBARI-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348943#comment-14348943 ]
Hari Sekhon commented on AMBARI-8559: ------------------------------------- This is needed for rolling restarts too. I've done a manual rolling restart (need AMBARI-6706) and having restarted each Resource Manager individually and then done a rolling restart of NodeManagers, I'm left in a state where the configs aren't deployed with the new configuration and I'm unable to deploy them without this feature to clear the stale configuration. > Deploy Config without service restart > ------------------------------------- > > Key: AMBARI-8559 > URL: https://issues.apache.org/jira/browse/AMBARI-8559 > Project: Ambari > Issue Type: Improvement > Affects Versions: 1.6.1, 1.7.0 > Environment: HDP 2.1 & HDP 2.2 > Reporter: Hari Sekhon > > Feature request for "Deploy Config" button - without doing a service restart. > Not all config changes require a service restart (eg. a client side option > change or when changing NFS gateway setup there is no point in bouncing all > the NameNode and DataNodes). > It's more work to figure out what settings affect which components (and > probably impractical), but it's sufficient to provide "Deploy Config" and > leave the service marked with stale config for restart for a later time. > This is analagous to Cloudera Manager's "Deploy Client Configuration" button. > Regards, > Hari Sekhon > (ex-Cloudera) > http://www.linkedin.com/in/harisekhon -- This message was sent by Atlassian JIRA (v6.3.4#6332)