[
https://issues.apache.org/jira/browse/YARN-7509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-7509:
-----------------------------
Priority: Critical (was: Major)
> AsyncScheduleThread and ResourceCommitterService are still running after RM
> is transitioned to standby
> ------------------------------------------------------------------------------------------------------
>
> Key: YARN-7509
> URL: https://issues.apache.org/jira/browse/YARN-7509
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.0.0-alpha4, 2.9.1
> Reporter: Tao Yang
> Assignee: Tao Yang
> Priority: Critical
> Fix For: 3.1.0, 2.9.1, 3.0.1
>
> Attachments: YARN-7509.001.patch
>
>
> After RM is transitioned to standby, AsyncScheduleThread and
> ResourceCommitterService will receive interrupt signal. When thread is
> sleeping, it will ignore the interrupt signal since InterruptedException is
> catched inside and the interrupt signal is cleared.
> For AsyncScheduleThread, InterruptedException was catched and ignored in
> CapacityScheduler#schedule.
> For ResourceCommitterService, InterruptedException was catched inside and
> ignored in ResourceCommitterService#run.
> We should let the interrupt signal out and make these threads exit.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
