hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-5566) Client-side NM graceful decom is not triggered when jobs finish
Date Tue, 06 Sep 2016 20:33:20 GMT

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

Robert Kanter updated YARN-5566:
    Attachment: YARN-5566.004.branch-2.8.patch

Thanks for the reviews [~djp] and [~kasha].  I've just attached a version of the patch for
branch-2.8.  It steals a few unit tests (with some minor modifications) from YARN-4676, and
it deletes the old code from {{StatusUpdateWhenHealthyTransition}} for transitioning to {{DECOMMISSIONED}}
(originally done by YARN-4676) in favor of the new code added by this JIRA.

> Client-side NM graceful decom is not triggered when jobs finish
> ---------------------------------------------------------------
>                 Key: YARN-5566
>                 URL: https://issues.apache.org/jira/browse/YARN-5566
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.8.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>             Fix For: 2.9.0, 3.0.0-alpha2
>         Attachments: YARN-5566.001.patch, YARN-5566.002.patch, YARN-5566.003.patch, YARN-5566.004.branch-2.8.patch,
> I was testing the client-side NM graceful decommission and noticed that it was always
waiting for the timeout, even if all jobs running on that node (or even the cluster) had already
> For example:
> # JobA is running with at least one container on NodeA
> # User runs client-side decom on NodeA at 5:00am with a timeout of 3 hours --> NodeA
> # JobA finishes at 6:00am and there are no other jobs running on NodeA
> # User's client reaches the timeout at 8:00am, and forcibly decommissions NodeA
> NodeA should have decommissioned at 6:00am.

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