hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xuan Gong (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-6440) re-visit handling QUEUE-STOP process
Date Tue, 04 Apr 2017 22:54:41 GMT

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

Xuan Gong updated YARN-6440:
    Attachment: YARN-6440.1.patch

> 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
>         Attachments: YARN-6440.1.patch
> 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

This message was sent by Atlassian JIRA

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

View raw message