You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2014/02/25 01:44:19 UTC
[jira] [Commented] (AMBARI-4810) Bulk decommissioning multiple
slaves makes it look like only one slave is being decommissioned
[ https://issues.apache.org/jira/browse/AMBARI-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13911050#comment-13911050 ]
Yusaku Sako commented on AMBARI-4810:
-------------------------------------
+1 for the patch.
> Bulk decommissioning multiple slaves makes it look like only one slave is being decommissioned
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-4810
> URL: https://issues.apache.org/jira/browse/AMBARI-4810
> Project: Ambari
> Issue Type: Task
> Components: client
> Affects Versions: 1.5.0
> Reporter: Xi Wang
> Assignee: Xi Wang
> Fix For: 1.5.0
>
> Attachments: AMBARI-4810.patch
>
>
> Modify the Decom/Recom task names in BGO popup:
> "Decommission, Excluded: host1,host2 ..." should be "Decommission: host1,host2.."
> "Decommission, Included: host1,host2 ..." should be "Recommission: host1,host2.."
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)