You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "Viraj Jasani (JIRA)" <ji...@apache.org> on 2019/06/15 10:45:00 UTC

[jira] [Updated] (AMBARI-25209) Bulk Operation Refresh Configs for selected hosts

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

Viraj Jasani updated AMBARI-25209:
----------------------------------
    Affects Version/s:     (was: 2.6.2)

> Bulk Operation Refresh Configs for selected hosts
> -------------------------------------------------
>
>                 Key: AMBARI-25209
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25209
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-web
>    Affects Versions: trunk, 2.7.4
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: trunk, 2.6.2, 2.7.4
>
>          Time Spent: 4.5h
>  Remaining Estimate: 0h
>
> There are multiple requirements of performing Refresh Configs after some config update or as a recovery from failures. This operation should be provided as a bulk operation on selective hosts so that all client components can be refreshed on all selected hosts.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)