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

Posted to issues@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2016/07/14 18:00:23 UTC

[jira] [Updated] (AMBARI-15470) List of decommission-allowed components should be stack driven

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

Yusaku Sako updated AMBARI-15470:
---------------------------------
    Fix Version/s:     (was: trunk)
                   2.4.0

> List of decommission-allowed components should be stack driven
> --------------------------------------------------------------
>
>                 Key: AMBARI-15470
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15470
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server, ambari-web
>    Affects Versions: trunk
>            Reporter: Di Li
>            Assignee: Di Li
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15470.patch
>
>
> decommission-allowed components are currently a hardcoded list in stack_service_component.js
> isDecommissionAllowed: Em.computed.existsIn('componentName', ['DATANODE', 'TASKTRACKER', 'NODEMANAGER', 'HBASE_REGIONSERVER']),
> This should be stack driven by examine metainfo.xml looking for DECOMMISSION custom command or a designated flag.



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