[
https://issues.apache.org/jira/browse/YARN-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil G updated YARN-4865:
--------------------------
Attachment: 0003-YARN-4865.patch
Thanks [~leftnoteasy] for the comments.
Yes, I can pull those null checks out for better readability. Updating a patch
for same.
bq.cost for reserve container is low.
Yes, I agree to this point very much. But when we do an app move, may be
target queue might be not be lowest used queues, and there for the moved app
may have to wait.
So if in case there were some container reserved for this app, after move it
may not get that very fast (may need to settle for rack local). But its not a
core/major issue, rather I think its nice to have enhancement if supported.
> Track Reserved resources in ResourceUsage and QueueCapacities
> --------------------------------------------------------------
>
> Key: YARN-4865
> URL: https://issues.apache.org/jira/browse/YARN-4865
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.7.2
> Reporter: Sunil G
> Assignee: Sunil G
> Attachments: 0001-YARN-4865.patch, 0002-YARN-4865.patch,
> 0003-YARN-4865.patch
>
>
> As discussed in YARN-4678, capture reserved capacity separately in
> QueueCapcities for better tracking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
