hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tao Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7003) DRAINING state of queues can't be recovered after RM restart
Date Thu, 10 May 2018 15:41:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470564#comment-16470564

Tao Yang commented on YARN-7003:

UT failures seems irrelative with this patch. Attached v4 patch to fix check-style warning
and trigger again.

> DRAINING state of queues can't be recovered after RM restart
> ------------------------------------------------------------
>                 Key: YARN-7003
>                 URL: https://issues.apache.org/jira/browse/YARN-7003
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.9.0, 3.0.0-alpha4
>            Reporter: Tao Yang
>            Assignee: Tao Yang
>            Priority: Major
>         Attachments: YARN-7003.001.patch, YARN-7003.002.patch, YARN-7003.003.patch, YARN-7003.004.patch
> DRAINING state is a temporary state in RM memory, when queue state is set to be STOPPED
but there are still some pending or active apps in it, the queue state will be changed to
DRAINING instead of STOPPED after refreshing queues. We've encountered the problem that the
state of this queue will aways be STOPPED after RM restarted, so that it can be removed at
any time and leave some apps in a non-existing queue.
> To fix this problem, we could recover DRAINING state in the recovery process of pending/active
apps. I will upload a patch with test case later for review.

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