[
https://issues.apache.org/jira/browse/YARN-11398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18033729#comment-18033729
]
ASF GitHub Bot commented on YARN-11398:
---------------------------------------
github-actions[bot] commented on PR #5233:
URL: https://github.com/apache/hadoop/pull/5233#issuecomment-3459165820
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> 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]
