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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2016/06/09 21:06:21 UTC

[jira] [Commented] (YARN-314) Schedulers should allow resource requests of different sizes at the same priority and location

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

Jason Lowe commented on YARN-314:
---------------------------------

bq. Do we have applications that need this capability?

Tez can sometimes end up asking for multiple sizes at the same priority, and that sometimes ends up causing jobs to hang.  See TEZ-3296.

> Schedulers should allow resource requests of different sizes at the same priority and location
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-314
>                 URL: https://issues.apache.org/jira/browse/YARN-314
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>         Attachments: yarn-314-prelim.patch
>
>
> Currently, resource requests for the same container and locality are expected to all be the same size.
> While it it doesn't look like it's needed for apps currently, and can be circumvented by specifying different priorities if absolutely necessary, it seems to me that the ability to request containers with different resource requirements at the same priority level should be there for the future and for completeness sake.



--
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