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 2013/05/01 03:25:13 UTC
[jira] [Commented] (AMBARI-2060) Initiate a recommission, on
success, the operations dialog says decommission, not recommission
[ https://issues.apache.org/jira/browse/AMBARI-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13646271#comment-13646271 ]
Yusaku Sako commented on AMBARI-2060:
-------------------------------------
Since the backend uses the same action "DECOMMISSION_DATANODE" for decommission and recommission, the frontend will display "Update Exclude File" that would make sense in both scenarios.
> Initiate a recommission, on success, the operations dialog says decommission, not recommission
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-2060
> URL: https://issues.apache.org/jira/browse/AMBARI-2060
> Project: Ambari
> Issue Type: Bug
> Components: client
> Affects Versions: 1.3.0
> Reporter: Yusaku Sako
> Assignee: Yusaku Sako
> Fix For: 1.3.0
>
> Attachments: Screen Shot 2013-04-30 at 5.23.26 PM.png, Screen Shot 2013-04-30 at 5.23.32 PM.png, Screen Shot 2013-04-30 at 5.23.40 PM.png
>
>
> See attached. Note that the request context is set to "Recommission DataNode", but it shows "Decommission DataNode execute" at the task level.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira