[
https://issues.apache.org/jira/browse/YARN-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xuan Gong updated YARN-6440:
----------------------------
Description:
Currently, when we stop the parent queue, we would do the following:
1) check the number of active applications. If there is no active application,
we would mark the queue state as STOPPED. Otherwise, we mark the queue state as
DRAIN, and wait for all the active applications finish.
2) Do the same step for all its children.
So, in current process, we always change the state for parent queue first which
will not work in some scenarios, such as the reservation system. In the
reservation system, the plan queue will not have any active applications
immediately at the beginning. So, when we stop the queue, it would change the
queue state into STOPPED immediately which could cause problem.
> re-visit handling QUEUE-STOP process
> ------------------------------------
>
> Key: YARN-6440
> URL: https://issues.apache.org/jira/browse/YARN-6440
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Xuan Gong
> Assignee: Xuan Gong
>
> Currently, when we stop the parent queue, we would do the following:
> 1) check the number of active applications. If there is no active
> application, we would mark the queue state as STOPPED. Otherwise, we mark the
> queue state as DRAIN, and wait for all the active applications finish.
> 2) Do the same step for all its children.
> So, in current process, we always change the state for parent queue first
> which will not work in some scenarios, such as the reservation system. In the
> reservation system, the plan queue will not have any active applications
> immediately at the beginning. So, when we stop the queue, it would change the
> queue state into STOPPED immediately which could cause problem.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
