[ 
https://issues.apache.org/jira/browse/YARN-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Subramaniam Krishnan updated YARN-1712:
---------------------------------------
    Attachment: YARN-1712.2.patch

[~leftnoteasy] , good to hear that you got the full context. Thanks for 
reviewing the patch. I am uploading a new patch that has the following changes:
   * Fix the Log message.
   * Replace stale references to sessions with reservations, good catch.

The currentReservations might have new reservations which just start now & so 
were not active before. These will not yet have corresponding reservation 
queues in CapacityScheduler as we create them after sorting. This is done to 
ensure the what you highlighted earlier - we never exceed total capacity.

> Admission Control: plan follower
> --------------------------------
>
>                 Key: YARN-1712
>                 URL: https://issues.apache.org/jira/browse/YARN-1712
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler, resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>              Labels: reservations, scheduler
>         Attachments: YARN-1712.1.patch, YARN-1712.2.patch, YARN-1712.patch
>
>
> This JIRA tracks a thread that continuously propagates the current state of 
> an inventory subsystem to the scheduler. As the inventory subsystem store the 
> "plan" of how the resources should be subdivided, the work we propose in this 
> JIRA realizes such plan by dynamically instructing the CapacityScheduler to 
> add/remove/resize queues to follow the plan.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to