hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-3920) FairScheduler container reservation on a node should be configurable to limit it to large containers
Date Fri, 18 Sep 2015 20:59:06 GMT

     [ https://issues.apache.org/jira/browse/YARN-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun Suresh updated YARN-3920:
------------------------------
    Summary: FairScheduler container reservation on a node should be configurable to limit
it to large containers  (was: FairScheduler Reserving a node for a container should be configurable
to allow it used only for large containers)

> FairScheduler container reservation on a node should be configurable to limit it to large
containers
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3920
>                 URL: https://issues.apache.org/jira/browse/YARN-3920
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: fairscheduler
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-3920.004.patch, YARN-3920.004.patch, YARN-3920.004.patch, YARN-3920.004.patch,
YARN-3920.005.patch, yARN-3920.001.patch, yARN-3920.002.patch, yARN-3920.003.patch
>
>
> Reserving a node for a container was designed for preventing large containers from starvation
from small requests that keep getting into a node. Today we let this be used even for a small
container request. This has a huge impact on scheduling since we block other scheduling requests
until that reservation is fulfilled. We should make this configurable so its impact can be
minimized by limiting it for large container requests as originally intended. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message