[
https://issues.apache.org/jira/browse/AMBARI-7607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14157920#comment-14157920
]
Hudson commented on AMBARI-7607:
--------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #466 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/466/])
AMBARI-7607 Refresh queues should refresh both RMs in an HA scenario. (Andriy
Kostin via ababiichuk) (ababiichuk:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=d1c6476c8a8673f948b589c0436ffffff350f505)
* ambari-web/app/controllers/main/service/item.js
> Refresh queues should refresh both RMs in an HA scenario
> --------------------------------------------------------
>
> Key: AMBARI-7607
> URL: https://issues.apache.org/jira/browse/AMBARI-7607
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 1.7.0
>
> Attachments: AMBARI-7607.patch
>
>
> 1\. Configure RM HA
> 2\. change Capscheduler (just add a queue)
> 3\. execute refresh queues
> Refresh is performed against the active RM, so that clears the "restart
> required" from that component (correct). But then I have to "restart" the
> standby RM to clear the restart required.
> In RM HA scenario, when someone issues refresh queues, we should push config
> to both RMs and issue refresh against both RMs just to clear both "restart
> required".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
