hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wangda Tan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-8149) Revisit behavior of Re-Reservation in Capacity Scheduler
Date Wed, 11 Apr 2018 18:07:00 GMT
Wangda Tan created YARN-8149:

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

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

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

View raw message