[
https://issues.apache.org/jira/browse/YARN-5486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantinos Karanasos updated YARN-5486:
-----------------------------------------
Attachment: YARN-5486.002.patch
Rebasing against trunk and adding new patch, also including some more
changes/fixes.
Thanks for the feedback, [~subru].
Regarding the _LinkedHashMap_ in the {{OpportunisticContainerContext}}, we
actually need it to keep the ordering of the nodes. Least loaded nodes should
come first when iterating over the hashmap, as they should be preferred when
placing opportunistic containers.
I added checks for the ContainerTypes in
{{TestOpportunisticContainersAllocation}}, as you suggested.
I suggest to keep the existing sleep logic for now, if it's OK, since it does
not seem to make the code much cleaner in the particular cases it is used (also
chatted with [~chris.douglas] about this).
> Update OpportunisticContainerAllocatorAMService::allocate method to handle
> OPPORTUNISTIC container requests
> -----------------------------------------------------------------------------------------------------------
>
> Key: YARN-5486
> URL: https://issues.apache.org/jira/browse/YARN-5486
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Arun Suresh
> Assignee: Konstantinos Karanasos
> Attachments: YARN-5486.001.patch, YARN-5486.002.patch
>
>
> YARN-5457 refactors the Distributed Scheduling framework to move the
> container allocator to yarn-server-common.
> This JIRA proposes to update the allocate method in the new AM service to use
> the OpportunisticContainerAllocator to allocate opportunistic containers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
