Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 28 Feb 2014 14:13:19 +0000 (UTC)
From: "Andrii Babiichuk (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12697927.1393596538193.124485.1393596799070@arcas>
In-Reply-To: <JIRA.12697927.1393596538193@arcas>
References: <JIRA.12697927.1393596538193@arcas>
Subject: [jira] [Updated] (AMBARI-4882) Bulk Ops: decommissioning a slave
 component on multiple hosts silently fails on UI if at least one is stopped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ 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)