hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3769) Preemption occurring unnecessarily because preemption doesn't consider user limit
Date Mon, 16 Nov 2015 18:38:11 GMT

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

Wangda Tan commented on YARN-3769:

[~eepayne], thanks for update:

bq. Would it be more efficient to just do the following? ... 
The problem is getUserResourceLimit is not always updated by scheduler. If a queue is not
traversed by scheduler OR apps of a queue-user have long heartbeat interval, the user resource
limit could be staled.

I found 0005 patch for trunk is computing user-limit every time and 0005 patch for 2.7 is
using getUserResourceLimit.


> Preemption occurring unnecessarily because preemption doesn't consider user limit
> ---------------------------------------------------------------------------------
>                 Key: YARN-3769
>                 URL: https://issues.apache.org/jira/browse/YARN-3769
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.6.0, 2.7.0, 2.8.0
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>         Attachments: YARN-3769-branch-2.002.patch, YARN-3769-branch-2.7.002.patch, YARN-3769-branch-2.7.003.patch,
YARN-3769-branch-2.7.005.patch, YARN-3769.001.branch-2.7.patch, YARN-3769.001.branch-2.8.patch,
YARN-3769.003.patch, YARN-3769.004.patch, YARN-3769.005.patch
> We are seeing the preemption monitor preempting containers from queue A and then seeing
the capacity scheduler giving them immediately back to queue A. This happens quite often and
causes a lot of churn.

This message was sent by Atlassian JIRA

View raw message