ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Sekhon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-8559) Deploy Config without service restart
Date Thu, 05 Mar 2015 15:41:38 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-8559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hari Sekhon updated AMBARI-8559:
--------------------------------
    Affects Version/s: 1.7.0

> 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
>            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)

Mime
View raw message