You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2014/02/22 01:04:20 UTC

[jira] [Updated] (AMBARI-4791) API call to restart all components on one or more hosts should result in one request

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

Siddharth Wagle updated AMBARI-4791:
------------------------------------

    Attachment: AMBARI-4791.patch

Preliminary patch.

> API call to restart all components on one or more hosts should result in one request
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-4791
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4791
>             Project: Ambari
>          Issue Type: Task
>          Components: controller
>    Affects Versions: 1.5.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4791.patch
>
>
> Currently, restarting all components (or all components that need config update) on a host (or multiple hosts) requires batching of multiple calls (one call per component type). This results in a whole bunch of requests being generated and floods the request history visible from the background operation popup.
> Restart should work in a similar way as "Start" and "Stop" for host components, where the FE can construct a single API call that results in a single request.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)