hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-6210) FS: Node reservations can interfere with preemption
Date Wed, 22 Feb 2017 18:19:44 GMT

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

Karthik Kambatla commented on YARN-6210:

bq. FSAppAttempt.isStarved(Resource usage, Resource share): probably a bad name. It doesn't
have anything to do with starving. It's a comparator.
I agree it is not the best name, but I couldn't come up with a better name that will not be
used incorrectly in the future. I am happy to accommodate any valid suggestions. 

bq. Nope, the assignment-at-lower-priority assert is retained. The original test also had
an assert to test the reservation itself:
This test deals in fewer containers. There is a check for reservation succeeding and subsequently
allocation succeeding. Since the behavior changed on when reservations are allowed, the app
cannot reserve more than one container.

> FS: Node reservations can interfere with preemption
> ---------------------------------------------------
>                 Key: YARN-6210
>                 URL: https://issues.apache.org/jira/browse/YARN-6210
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.9.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: YARN-6210.1.patch, YARN-6210.2.patch, YARN-6210.3.patch
> Today, on a saturated cluster, apps with pending demand reserve nodes. A new app might
not be able to preempt resources because these nodes are already reserved. This can be reproduced
by the example in YARN-6151. 
> Since node reservations are to prevent starvation of apps requesting large containers,
triggering these reservations only on starved applications would avoid this situation. 

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