[
https://issues.apache.org/jira/browse/YARN-9642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16915955#comment-16915955
]
Bibin A Chundatt commented on YARN-9642:
----------------------------------------
[~tangzhankun] and [~rohithsharma]
Tried running it locally
{code}
INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M1:test (default-test) @
hadoop-yarn-server-resourcemanager ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestIncreaseAllocationExpirer
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 53.808 s
- in
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestIncreaseAllocationExpirer
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
{code}
Failure seems random
> AbstractYarnScheduler#clearPendingContainerCache could run even after
> transitiontostandby
> -----------------------------------------------------------------------------------------
>
> Key: YARN-9642
> URL: https://issues.apache.org/jira/browse/YARN-9642
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Priority: Blocker
> Labels: memory-leak
> Attachments: YARN-9642.001.patch, YARN-9642.002.patch,
> YARN-9642.003.patch, image-2019-06-22-16-05-24-114.png
>
>
> The TimeTask could hold the reference of Scheduler in case of fast switch
> over too.
> AbstractYarnScheduler should make sure scheduled Timer cancelled on
> serviceStop.
> Causes memory leak too
> !image-2019-06-22-16-05-24-114.png!
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
