You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Sunil G (JIRA)" <ji...@apache.org> on 2016/05/03 14:51:12 UTC

[jira] [Commented] (YARN-5031) Add a conf to disable container reservation

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

Sunil G commented on YARN-5031:
-------------------------------

Container reservation is by far helps in many cases. In a heterogeneous cluster, where different types applications were running, I am not very sure about a configuration which disables reservation in scheduler level. As per the use case, this scenario looks like more of application specific. Since queues gives only a logical view of resources, and reservation happens on node, we need to see how better output we can get for a queue level config. 
A suggestion, I feel preemption can help here if in case queue is under served and other queues requests were reserved on node. Thoughts?

> Add a conf to disable container reservation
> -------------------------------------------
>
>                 Key: YARN-5031
>                 URL: https://issues.apache.org/jira/browse/YARN-5031
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: sandflee
>
> in a cluster with long running services,  container reservation may starve other small request services



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org