[
https://issues.apache.org/jira/browse/AMBARI-19216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15764256#comment-15764256
]
Hudson commented on AMBARI-19216:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.5 #559 (See
[https://builds.apache.org/job/Ambari-branch-2.5/559/])
AMBARI-19216 After rescanning yarn queue, Ambari still asks for RM to be (dsen:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=bd56b2add417dfc6257669ee44622fdb71655297])
* (edit) ambari-agent/src/test/python/ambari_agent/TestActionQueue.py
* (edit) ambari-agent/src/main/python/ambari_agent/ActionQueue.py
> 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_2.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)
