ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15470) List of decommission-allowed components should be stack driven
Date Tue, 05 Apr 2016 15:36:25 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-15470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226470#comment-15226470
] 

Hadoop QA commented on AMBARI-15470:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12797090/AMBARI-15470.patch
  against trunk revision .

    {color:red}-1 patch{color}.  Top-level trunk compilation may be broken.

Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/6225//console

This message is automatically generated.

> 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: trunk
>
>         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)

Mime
View raw message