[
https://issues.apache.org/jira/browse/YARN-6180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867207#comment-15867207
]
Arun Suresh commented on YARN-6180:
-----------------------------------
Yup, this is meant to track for container updates in general.
Anyway, I was going thru YARN-5540 again, and it looks like the changes in the
{{AppScheduleingInfo::decrementOutstanding()}} does infact clean up
schedulerKeys whose numContainers are 0.. the AM does not need to explicitly
send a 0 container ResourceRequest. Since Container Updates are just another
SchedulerKey (well the ExecutionType Updates currently... we still need to move
the increase container plumbing from the AppSchedulingInfo into the
ContainerUpdateContext).
I will verify the above with a testcase to verify the expected behavior and
either close this as not an issue or add a testcase only patch for this.
> Clean unused SchedulerRequestKeys once ExecutionType updates are completed
> --------------------------------------------------------------------------
>
> Key: YARN-6180
> URL: https://issues.apache.org/jira/browse/YARN-6180
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Arun Suresh
>
> The SchedulerRequestKeys used for ExecutionType updates, that are generated,
> tend to accumulate in the AppSchedulingInfo and over time lead to a situation
> outlined in YARN-5540.
> These keys must be removed once the container update completes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
