Tao Yang created YARN-9580:
------------------------------
Summary: Fulfilled reservation information in assignment is lost
when transferring in ParentQueue#assignContainers
Key: YARN-9580
URL: https://issues.apache.org/jira/browse/YARN-9580
Project: Hadoop YARN
Issue Type: Bug
Components: capacityscheduler
Reporter: Tao Yang
Assignee: Tao Yang
When transferring assignment from child queue to parent queue, fulfilled
reservation information including fulfilledReservation and
fulfilledReservedContainer in assignment is lost.
When multi-nodes enabled, this lost can raise a problem that allocation
proposal is generated but can't be accepted because there is a check for
fulfilled reservation information in
FiCaSchedulerApp#commonCheckContainerAllocation, this endless loop will always
be there and the resource of the node can't be used anymore.
In HB-driven scheduling mode, fulfilled reservation can be allocated via
another calling stack: CapacityScheduler#allocateContainersToNode -->
CapacityScheduler#allocateContainerOnSingleNode -->
CapacityScheduler#allocateFromReservedContainer, in this way assignment can be
generated by leaf queue and directly submitted, I think that's why we hardly
find this problem before.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
