hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil G (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6538) Inter Queue preemption is not happening when DRF is configured
Date Sat, 29 Apr 2017 00:16:04 GMT

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

Sunil G updated YARN-6538:
--------------------------
    Description: 
Cluster capacity of <memory:3TB, vCores:168>. Here memory is more and vcores are less.
If applications have more demand, vcores might be exhausted. 
Inter queue preemption ideally has to be kicked in once vcores is over utilized. However preemption
is not happening.

Analysis:
In {{AbstractPreemptableResourceCalculator.computeFixpointAllocation}}, 
{code}
    // assign all cluster resources until no more demand, or no resources are
    // left
    while (!orderedByNeed.isEmpty() && Resources.greaterThan(rc, totGuarant,
        unassigned, Resources.none())) {
{code}
 will loop even when vcores are 0 (because memory is still +ve). Hence we are having more
vcores in idealAssigned which cause no-preemption cases.

  was:
Cluster capacity of <memory:3TB, vCores:168>. Here memory is more and vcores are less.
If applications have more demand, vcores might be exhausted. 
Inter queue preemption ideally has to be kicked in once vcores is over utilized. However preemption
is not happening.

Analysis:
In {{AbstractPreemptableResourceCalculator.computeFixpointAllocation}}, 
{code}
    // assign all cluster resources until no more demand, or no resources are
    // left
    while (!orderedByNeed.isEmpty() && Resources.greaterThan(rc, totGuarant,
        unassigned, Resources.none())) {
{code}
 will loop even when vcores are 0. Hence we are having more vcores in idealAssigned which
cause no-preemption cases.


> Inter Queue preemption is not happening when DRF is configured
> --------------------------------------------------------------
>
>                 Key: YARN-6538
>                 URL: https://issues.apache.org/jira/browse/YARN-6538
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler, scheduler preemption
>    Affects Versions: 2.8.0
>            Reporter: Sunil G
>            Assignee: Sunil G
>
> Cluster capacity of <memory:3TB, vCores:168>. Here memory is more and vcores are
less. If applications have more demand, vcores might be exhausted. 
> Inter queue preemption ideally has to be kicked in once vcores is over utilized. However
preemption is not happening.
> Analysis:
> In {{AbstractPreemptableResourceCalculator.computeFixpointAllocation}}, 
> {code}
>     // assign all cluster resources until no more demand, or no resources are
>     // left
>     while (!orderedByNeed.isEmpty() && Resources.greaterThan(rc, totGuarant,
>         unassigned, Resources.none())) {
> {code}
>  will loop even when vcores are 0 (because memory is still +ve). Hence we are having
more vcores in idealAssigned which cause no-preemption cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message