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

Posted to dev@ambari.apache.org by "Henry Sowell (JIRA)" <ji...@apache.org> on 2015/12/16 05:20:46 UTC

[jira] [Updated] (AMBARI-14395) Restarting all affected services

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

Henry Sowell updated AMBARI-14395:
----------------------------------
    Affects Version/s: trunk

> Restarting all affected services
> --------------------------------
>
>                 Key: AMBARI-14395
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14395
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-web
>    Affects Versions: trunk
>            Reporter: Henry Sowell
>            Priority: Minor
>              Labels: features
>
> If any change or error occurs that affects multiple services on the cluster you now have a couple of options to go in and restart the affected service:
> - From the dashboard, select "Actions", Stop All, and then Start All (not recommended)
> - You can go into each service individually restarting the affected service
> This is unnecessary, burdensome, and can potentially lead to problems on the cluster. I would recommend adding a selection to the "Actions" drop-down for "Restart affected services". This would prevent users from having to go into each service to perform restarts and from them using the hammer of stop all start all.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)