hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunil Govindan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-8149) Revisit behavior of Re-Reservation in Capacity Scheduler
Date Sat, 17 Nov 2018 03:24:08 GMT

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

Sunil Govindan updated YARN-8149:
---------------------------------
    Target Version/s: 3.3.0  (was: 3.2.0)

Bulk update: moved all 3.2.0 non-blocker issues, please move back if it is a blocker.

> Revisit behavior of Re-Reservation in Capacity Scheduler
> --------------------------------------------------------
>
>                 Key: YARN-8149
>                 URL: https://issues.apache.org/jira/browse/YARN-8149
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Wangda Tan
>            Priority: Major
>
> Frankly speaking, I'm not sure why we need the re-reservation. The formula is not that
easy to understand:
> Inside: {{org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.allocator.RegularContainerAllocator#shouldAllocOrReserveNewContainer}}
> {code:java}
> starvation = re-reservation / (#reserved-container * 
>      (1 - min(requested-resource / max-alloc, 
>               max-alloc - min-alloc / max-alloc))
> should_allocate = starvation + requiredContainers - reservedContainers > 0{code}
> I think we should be able to remove the starvation computation, just to check requiredContainers
> reservedContainers should be enough.
> In a large cluster, we can easily overflow re-reservation to MAX_INT, see YARN-7636. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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