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] [Commented] (YARN-7248) NM returns new SCHEDULED container status to older clients
Date Mon, 25 Sep 2017 18:05:00 GMT

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

Arun Suresh commented on YARN-7248:

Ah yes, we had included LOCALIZING in the reported SCHEDULED state as well.

bq. Another way to tackle this is to move the subset of states related to RUNNING into another
enum rather than extending the existing one
I like this, Let me give this a shot. Essentially, I will:
# remove the api.records.ContainerState.SCHEDULED state completely
# Add a new api record, say  {{api.records.ContainerSubState}} ? which can have LOCALIZING,
LOCALIZING_FAILED, SCHEDULED, PAUSED, RESUMING etc. which will be returned along with the
container status, which clients can choose to ignore.

Sounds good ? 

> 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
>            Priority: Blocker
> 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