You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Arun Suresh (JIRA)" <ji...@apache.org> on 2017/12/28 16:49:00 UTC

[jira] [Commented] (YARN-7542) NM recovers some Running Opportunistic Containers as SUSPEND

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

Arun Suresh commented on YARN-7542:
-----------------------------------

Thanks for investigating and for the patch [~sampada].
pretty straightforward so +1. Testing this specific case looks to be non-trivial, so let tackle testing {{ContainersLauncher}} properly in a separate JIRA.

> NM recovers some Running Opportunistic Containers as SUSPEND
> ------------------------------------------------------------
>
>                 Key: YARN-7542
>                 URL: https://issues.apache.org/jira/browse/YARN-7542
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Arun Suresh
>            Assignee: Sampada Dehankar
>         Attachments: YARN-7542.001.patch
>
>
> Steps to reproduce:
> * Start YARN cluster - Enable Opportunistic containers and set NM queue length to something > 10. Also Enable work preserving restart
> * Start an MR job (without opportunistic containers)
> * Kill the NM and restart it again.
> * In the logs - it shows that some of the containers are in SUSPENDED state - even though they are still running.
> [~sampada15] / [~kartheek], can you take a look at this ?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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