You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/06/19 08:15:00 UTC
[jira] [Commented] (AMBARI-25209) Bulk Operation Refresh Configs
for selected hosts
[ https://issues.apache.org/jira/browse/AMBARI-25209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867333#comment-16867333 ]
Hudson commented on AMBARI-25209:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10500 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10500/])
AMBARI-25209 : Bulk Operation Refresh Configs for selected hosts (#2891) (asnaik: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=076279cc91d7b2851c67ac6b8979e4eda4e28fc4])
* (edit) ambari-web/app/messages.js
* (edit) ambari-web/app/controllers/main/host/bulk_operations_controller.js
* (edit) ambari-web/app/views/main/host/hosts_table_menu_view.js
> 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.7.4
>
> Time Spent: 6h 10m
> 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)