[
https://issues.apache.org/jira/browse/AMBARI-19216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15752191#comment-15752191
]
Hadoop QA commented on AMBARI-19216:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12843442/AMBARI-19216.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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/9696//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9696//console
This message is automatically generated.
> After rescanning yarn queue, Ambari still asks for RM to be restarted
> ---------------------------------------------------------------------
>
> Key: AMBARI-19216
> URL: https://issues.apache.org/jira/browse/AMBARI-19216
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Dmytro Sen
> Assignee: Dmytro Sen
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-19216.patch
>
>
> Ran into this while troubleshooting a yarn issue.
> 1. Go to yarn view, and change any value in one of your queues.
> 2. Save and Refresh queues
> 3 Go to Yarn service. It now says RM needs to be restarted (***This is false,
> and did not flag in 2.2.x versions of Ambari***)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
