hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-7248) NM returns new SCHEDULED container status to older clients
Date Mon, 25 Sep 2017 20:59:00 GMT

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

Arun Suresh updated YARN-7248:
    Attachment: YARN-7248.001.patch

Attaching initial patch based on discussions above.
* Removed the SCHEDULED and PAUSED states from api.records.ContainerState.
* ContainerStatus already seems to have a map<string, string> of container attributes
used to send the IP and host etc. I added an extra string key called "ExtraStateInfo" which
contains the stringified internal conatiner state as well. [~jlowe], I guess this should make
it more extensible that having a new enum ?
* Updated all the test cases.

> NM returns new SCHEDULED container status to older clients
> ----------------------------------------------------------
>                 Key: YARN-7248
>                 URL: https://issues.apache.org/jira/browse/YARN-7248
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: nodemanager
>    Affects Versions: 2.9.0, 3.0.0-alpha2
>            Reporter: Jason Lowe
>            Assignee: Arun Suresh
>            Priority: Blocker
>         Attachments: YARN-7248.001.patch
> YARN-4597 added a new SCHEDULED container state and that state is returned to clients
when the container is localizing, etc.  However the client may be running on an older software
version that does not have the new SCHEDULED state which could lead the client to crash on
the unexpected container state value or make incorrect assumptions like any state != NEW and
!= RUNNING must be COMPLETED which was true in the older version.

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