[
https://issues.apache.org/jira/browse/AMBARI-9976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14355179#comment-14355179
]
Hadoop QA commented on AMBARI-9976:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12703679/AMBARI-9976.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1988//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1988//console
This message is automatically generated.
> Host component action dropdown should show all supported custom commands for
> that service component
> ---------------------------------------------------------------------------------------------------
>
> Key: AMBARI-9976
> URL: https://issues.apache.org/jira/browse/AMBARI-9976
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 1.7.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.1.0
>
> Attachments: AMBARI-9976.patch
>
>
> After resolution for https://issues.apache.org/jira/browse/AMBARI-6698,
> supported custom command for the service component is available via API.
> Custom action subscribed to a component and available in the API should be
> shown under component dropdown action menu.
> *Exception:* decommission and recommission actions will be the exception
> where we show the custom command on slave component of the service instead of
> the actual component on which the command is subscribed in stack definition
> and eventually executed.
> *Note:* If a master component has the max limit for cardinality of more than
> 1 and has the custom command affiliated to itself then find the number of
> hostcomponents installed for that component in the cluster and if it's
> greater than 1 then find the active host component and only enable the link
> for custom commands on active component.
> If there is no active component even though there are more than one master
> component installed then show the custom command link on all master
> components (this specific requirement is to support the scenario where a
> component can have multiple instances in the cluster even though component or
> ambari does not hold the notion of HA for it like ZK servers)
> *Verification of the patch:*
> On resolution of this patch, Yarn refresh queue command will automatically
> appear for Active Resource Manager component action menu.
> After enabling ResourceManager HA, the command link for "Refresh Queue" will
> be enabled only on active RM
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
