[
https://issues.apache.org/jira/browse/YARN-6406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951418#comment-15951418
]
Wangda Tan commented on YARN-6406:
----------------------------------
Nice catch [[email protected]].
[~asuresh]/[~jlowe], I totally agree to remove it once #pending-req = 0.
[~jlowe], IIRC, the reference number for scheduler key is added because we have
two different request before: increase request and resource request. There's a
change [[email protected]] did recently is, remove the increase request,
now all increase request becomes a normal resource request. Regarding to this,
I don't think we need the #ref any more, correct? To me a set of SchedulerKey
will be good enough.
Please share your thoughts.
> Garbage Collect unused SchedulerRequestKeys
> -------------------------------------------
>
> Key: YARN-6406
> URL: https://issues.apache.org/jira/browse/YARN-6406
> Project: Hadoop YARN
> Issue Type: Improvement
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
> YARN-5540 introduced some optimizations to remove satisfied SchedulerKeys
> from the AppScheduleingInfo. It looks like after YARN-6040,
> ScedulerRequestKeys are removed only if the Application sends a 0
> numContainers requests. While earlier, the outstanding schedulerKeys were
> also remove as soon as a container is allocated as well.
> An additional optimization we were hoping to include is to remove the
> ResourceRequests itself once the numContainers == 0, since we see in our
> clusters that the RM heap space consumption increases drastically due to a
> large number of ResourceRequests with 0 num containers.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
