tez-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gopal V (JIRA)" <j...@apache.org>
Subject [jira] [Created] (TEZ-3872) OneToOne Edge: Scheduling misses due to released containers
Date Sun, 03 Dec 2017 08:30:00 GMT
Gopal V created TEZ-3872:

             Summary: OneToOne Edge: Scheduling misses due to released containers
                 Key: TEZ-3872
                 URL: https://issues.apache.org/jira/browse/TEZ-3872
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Gopal V


That's where it decides between using container or node/racks - it does not record the hosts/racks
for the container, the container affinity ignores node affinity fall backs.


Inside the YARN task scheduling impl, this only picks up the host if the container is being
held at the moment, not if it has been released - this also has no checks for in use containers.

TaskSchedulerManager can grab  ta.containerNodeId, directly off the attempt information to
get the host info as well container info.

This needs a new allocateTask API which has container, host, rack in the order of scheduling

This message was sent by Atlassian JIRA

View raw message