[
https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751428#comment-17751428
]
ASF GitHub Bot commented on YARN-11398:
---------------------------------------
bitterfox commented on PR #5233:
URL: https://github.com/apache/hadoop/pull/5233#issuecomment-1667087108
Hi, any update on this PR? We're also suffering high CPU usage in low-spec
clusters like alpha and beta environments with yarn.
WDYT to wait for some signal in `run()` while loop when `futures` is empty
instead of sleeping if you don't like sleep?
We can fire signal from
https://github.com/apache/hadoop/blob/55e8301470e2b8bed8ac2cc66f01398a51e0fa23/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/security/DelegationTokenRenewer.java#L230
> ResourceManager DelegationTokenRenewer timeout feature may cause high
> utilization of CPU and object leak.
> ---------------------------------------------------------------------------------------------------------
>
> Key: YARN-11398
> URL: https://issues.apache.org/jira/browse/YARN-11398
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 3.3.1, 3.3.2, 3.3.3, 3.3.4
> Reporter: Daniel Ma
> Priority: Major
> Labels: pull-request-available
>
> ResourceManager DelegationTokenRenewer timeout feature may cause high
> utilization of CPU and object leak.
> 1-If yarn cluster is in idle state, that is almost no token renewer event
> triggered, the DelegationTokenRenewerPoolTracker thread will do nothing but
> dead loop, it will cause high CPU utilization.
> 2-The renewer event is hold in a map named futures, there is no removal logic
> , the map will become increasingly big with time going by.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
