[
https://issues.apache.org/jira/browse/YARN-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758120#comment-16758120
]
Wilfred Spiegelenburg commented on YARN-1655:
---------------------------------------------
I have started working on this already. I have a working code change for trunk
based on the changes from YARN-6216. YARN-6216 by itself is not enough to
implement the resizing, we do need some FS changes.
The only thing that is still bothering me is a new junit test I wrote that
keeps failing. The failure is caused by lingering resource requests. There does
not seem to be a proper clean up of resource requests in all cases. This only
seems to happen when an increase results in a reservation. If we then later
cancel or the increase request that caused the reservation it leaves the _node_
and _rack_ request behind and just removes the _any_ part of the request. This
looks similar to what is mentioned in YARN-5540 around leaving requests behind
which should not be there.
This issue does affect both schedulers but does not seem to cause a junit
failure in the capacity scheduler.
> Add implementations to FairScheduler to support increase/decrease container
> resource
> ------------------------------------------------------------------------------------
>
> Key: YARN-1655
> URL: https://issues.apache.org/jira/browse/YARN-1655
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Wangda Tan
> Assignee: Wilfred Spiegelenburg
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
