You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-dev@hadoop.apache.org by "Shilun Fan (Jira)" <ji...@apache.org> on 2024/04/01 23:49:00 UTC
[jira] [Resolved] (YARN-11663) [Federation] Add Cache Entity Nums Limit.
[ https://issues.apache.org/jira/browse/YARN-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shilun Fan resolved YARN-11663.
-------------------------------
Fix Version/s: 3.4.1
3.5.0
Target Version/s: 3.4.0
Assignee: Shilun Fan
Resolution: Fixed
> [Federation] Add Cache Entity Nums Limit.
> -----------------------------------------
>
> Key: YARN-11663
> URL: https://issues.apache.org/jira/browse/YARN-11663
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: federation, yarn
> Affects Versions: 3.4.0
> Reporter: Yuan Luo
> Assignee: Shilun Fan
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.1, 3.5.0
>
> Attachments: image-2024-03-14-18-12-28-426.png, image-2024-03-14-18-12-49-950.png, image-2024-03-15-10-50-32-860.png
>
>
> !image-2024-03-14-18-12-28-426.png!
> !image-2024-03-14-18-12-49-950.png!
> hi [~slfan1989] After apply this feature to our prod env, I found the memory of the router keeps growing over time. This is because after jobs finished, we won't access the expired key to trigger cleanup mechanism. Is it better to add cache maximum number limit？
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-dev-help@hadoop.apache.org