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 "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/01/07 11:08:39 UTC

[jira] [Updated] (YARN-4557) missed NonPartitioned Request Scheduling Opportunity is not correctly checking for all priorities of an app

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

Naganarasimha G R updated YARN-4557:
------------------------------------
    Attachment: YARN-4557.v1.001.patch

Fixing the above issues !

> missed NonPartitioned Request Scheduling Opportunity is not correctly checking for all priorities of an app
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-4557
>                 URL: https://issues.apache.org/jira/browse/YARN-4557
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api, client, resourcemanager
>            Reporter: Naganarasimha G R
>            Assignee: Naganarasimha G R
>            Priority: Minor
>         Attachments: YARN-4557.v1.001.patch
>
>
> When app has submitted requests for multiple priority in default partition, then if one of the priority requests has missed  non-partitioned-resource-request equivalent to cluster size then container needs to be allocated. Currently if the higher priority requests doesn't satisfy the condition, then whole application is getting skipped instead the priority



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