hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "yangzhangyang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1709) Admission Control: Reservation subsystem
Date Fri, 22 Dec 2017 12:15:05 GMT

    [ https://issues.apache.org/jira/browse/YARN-1709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301313#comment-16301313

yangzhangyang commented on YARN-1709:

Hi,  I want to ask you a question about reservation,  "Step 7 The Scheduler will then provide
containers from a special queue created to ensure resources reservation is respected. Within
the limits of the reservation, the user has guaranteed access to the resources, above that
resource sharing proceed with standard Capacity/Fairness sharing." When need reservation-job
comes with reservationId, what will happen if there is no real avail res on node manager,
just wait other am return res or direct preempt other running job's resource? thanks

> Admission Control: Reservation subsystem
> ----------------------------------------
>                 Key: YARN-1709
>                 URL: https://issues.apache.org/jira/browse/YARN-1709
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Subru Krishnan
>             Fix For: 2.6.0
>         Attachments: YARN-1709.patch, YARN-1709.patch, YARN-1709.patch, YARN-1709.patch,
YARN-1709.patch, YARN-1709.patch, YARN-1709.patch
> This JIRA is about the key data structure used to track resources over time to enable
YARN-1051. The Reservation subsystem is conceptually a "plan" of how the scheduler will allocate
resources over-time.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org

View raw message