[
https://issues.apache.org/jira/browse/YARN-7695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16309112#comment-16309112
]
stefanlee edited comment on YARN-7695 at 1/3/18 7:27 AM:
---------------------------------------------------------
i think this problem occured in
*transitionToStandby->createAndInitActiveServices->RMActiveServices.serviceInit->scheduler.reinitialize(conf,
rmContext)*, the *scheduler* is a new object?please correct me if i am
wrong.[~templedf]
was (Author: imstefanlee):
i think this problem occured in
*transitionToStandby->createAndInitActiveServices->RMActiveServices.serviceInit->scheduler.reinitialize(conf,
rmContext)*, the *scheduler* is a new object?please correct me if i am
wrong.[[email protected]]
> when active RM transit to standby , this RM will new another
> FairSchedulerUpdate Thread
> ---------------------------------------------------------------------------------------
>
> Key: YARN-7695
> URL: https://issues.apache.org/jira/browse/YARN-7695
> Project: Hadoop YARN
> Issue Type: Bug
> Components: fairscheduler, resourcemanager
> Affects Versions: 2.4.0
> Reporter: stefanlee
>
> 1. i test haoop-2.4.0 in my cluster.
> 2. RM1 is active and RM2 is standby
> 3. i delete /yarn-leader-election/Yarn/ActiveStandbyElectorLock from ZK
> 4. RM1 then transit from active to standby success.
> 5. at last ,i print RM1 jstack info and found two "AllocationFileReloader"
> and two "FairSchedulerUpdateThread" in RM1.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
