hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5829) FS preemption should reserve a node before considering containers on it for preemption
Date Mon, 13 Mar 2017 23:26:41 GMT

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

ASF GitHub Bot commented on YARN-5829:

Github user szegedim commented on a diff in the pull request:

    --- Diff: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSSchedulerNode.java
    @@ -110,6 +132,44 @@ synchronized FSAppAttempt getReservedAppSchedulable() {
    +   * List reserved resources after preemption and assign them to the
    +   * appropriate applications in a FIFO order.
    +   * @return if any resources were allocated
    +   */
    +  synchronized boolean assignContainersToPreemptionReservees() {
    --- End diff --
    The reason I brought it here is that we need to run it synchronized to make sure the list
does not change. The preemption reservation data belongs here I think. What I could do is
that do the assignContainersToPreemptionReservees tasks in fair scheduler and expose the lock
to that function.

> FS preemption should reserve a node before considering containers on it for preemption
> --------------------------------------------------------------------------------------
>                 Key: YARN-5829
>                 URL: https://issues.apache.org/jira/browse/YARN-5829
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: fairscheduler
>            Reporter: Karthik Kambatla
>            Assignee: Miklos Szegedi
> FS preemption evaluates nodes for preemption, and subsequently preempts identified containers.
If this node is not reserved for a specific application, any other application could be allocated
resources on this node. 
> Reserving the node for the starved application before preempting containers would help
avoid this.

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