You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/10/16 23:44:00 UTC
[jira] [Commented] (AMBARI-24791) Node Managers fail to start after
RM is moved to a different host as 'resource-tracker.address' config is not
updated
[ https://issues.apache.org/jira/browse/AMBARI-24791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16652666#comment-16652666 ]
Hudson commented on AMBARI-24791:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #10220 (See [https://builds.apache.org/job/Ambari-trunk-Commit/10220/])
[AMBARI-24791] Node Managers fail to start after RM is moved to a (ishanbhatt.1989: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=7110d4d965767e1bc98eb79bb12d1d42f65676d4])
* (edit) ambari-web/app/utils/configs/rm_ha_config_initializer.js
* (edit) ambari-web/app/data/configs/wizards/rm_ha_properties.js
* (edit) ambari-web/app/utils/configs/move_rm_config_initializer.js
* (edit) ambari-web/app/controllers/main/admin/highAvailability/resourceManager/step3_controller.js
> Node Managers fail to start after RM is moved to a different host as 'resource-tracker.address' config is not updated
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-24791
> URL: https://issues.apache.org/jira/browse/AMBARI-24791
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Reporter: Ishan Bhatt
> Assignee: Ishan Bhatt
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> # Under Yarn --> Service Actions - choose to Move Resource Manager. Pick a new host for the active RM node and let the move operation complete
> # Observe the state of Node Managers in Ambari UI
> *Result*
> All Node Managers show as down.
> Observed that one of the configs - 'yarn.resourcemanager.resource-tracker.address.rm2' still points to older RM node[!Screen Shot 2018-10-11 at 6.20.51 PM.png?default=false|thumbnail!|https://hortonworks.jira.com/secure/attachment/165347/165347_Screen+Shot+2018-10-11+at+6.20.51+PM.png] , which may be causing this issue
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)