ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Di Li (JIRA)" <j...@apache.org>
Subject [jira] [Created] (AMBARI-15470) List of decommission-allowed components should be stack driven
Date Thu, 17 Mar 2016 18:34:33 GMT
Di Li created AMBARI-15470:
------------------------------

             Summary: 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
             Fix For: trunk


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)

Mime
View raw message