[
https://issues.apache.org/jira/browse/YARN-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15064812#comment-15064812
]
Wangda Tan commented on YARN-4195:
----------------------------------
Hi [~curino],
Thanks for working on this, I've took a look at your description and patch.
Could you provide an example about GPU/PUBLICIP queue configuration and
resource request *when the proposal completed*? I may not understand it
competely, I guess it may look like:
- Since the system still uses partition to track resources, there're still 4
partitions: GPU_PUBLICIP, GPU_NOT-PUBLICIP, NOT-GPU_PUBLICIP,
NOT-GPU_NOT-PUBLICIP. Admin still needs to configure capacity of queues for the
4 partitions.
- Node label expression of Resource Request will be updated to partition, let's
say an expression = GPU, it becomes two resource requests internally:
GPU_PUBLICIP and PUBLICIP.
> Support of node-labels in the ReservationSystem "Plan"
> ------------------------------------------------------
>
> Key: YARN-4195
> URL: https://issues.apache.org/jira/browse/YARN-4195
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Carlo Curino
> Assignee: Carlo Curino
> Attachments: YARN-4195.patch
>
>
> As part of YARN-4193 we need to enhance the InMemoryPlan (and related
> classes) to track the per-label available resources, as well as the per-label
> reservation-allocations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
