hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Payne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5889) Improve user-limit calculation in capacity scheduler
Date Mon, 09 Jan 2017 17:02:59 GMT

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

Eric Payne commented on YARN-5889:

Thanks [~leftnoteasy] for your review and comments.

bq. If everybody agrees with approach in my comment
I agree. I think [~jlowe] summed it up well when he said your "... proposal ... preserves
the FIFO/priority behavior at least up through usage < MULP and then becomes fair once
a user is beyond MULP."

And in addition, we can add a UsersManager to LQ
And for last, we can look at logics for #active-users per partition, now we have an identical
#active-users for all partition
Let's please do these as separate JIRAs. We are extremely anxious to move this JIRA forward
since it is blocking YARN-2113 (user limit-based intra-queue preemption).

> Improve user-limit calculation in capacity scheduler
> ----------------------------------------------------
>                 Key: YARN-5889
>                 URL: https://issues.apache.org/jira/browse/YARN-5889
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: Sunil G
>            Assignee: Sunil G
>         Attachments: YARN-5889.0001.patch, YARN-5889.0001.suggested.patchnotes, YARN-5889.v0.patch,
YARN-5889.v1.patch, YARN-5889.v2.patch
> Currently user-limit is computed during every heartbeat allocation cycle with a write
lock. To improve performance, this tickets is focussing on moving user-limit calculation out
of heartbeat allocation flow.

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