[ https://issues.apache.org/jira/browse/YARN-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214504#comment-15214504 ]
Wangda Tan commented on YARN-4865: ---------------------------------- bq. 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. I think it's better to let scheduler decide if a container can be reserved or not after move. In above example, if a app move to a queue, but the app/queue have lower priority, we should let it wait to reserve containers. > 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)