ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrii Babiichuk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-4882) Bulk Ops: decommissioning a slave component on multiple hosts silently fails on UI if at least one is stopped
Date Fri, 28 Feb 2014 14:13:19 GMT

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

Andrii Babiichuk updated AMBARI-4882:
-------------------------------------

    Attachment: AMBARI-4882.patch

> Bulk Ops: decommissioning a slave component on multiple hosts silently fails on UI if
at least one is stopped
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-4882
>                 URL: https://issues.apache.org/jira/browse/AMBARI-4882
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-4882.patch
>
>
> To prevent such scenarios, we need to check if there are any components in INSTALLED
state, and list them out, saying these components are already stopped so decom will be skipped.
We don't want the user to force selecting the exact set of hosts with the slave components
in STARTED state.



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

Mime
View raw message