[
https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179337#comment-16179337
]
Arun Suresh commented on YARN-7248:
-----------------------------------
Thanks for raising this [~jlowe]. So, given that old clients only ask for (and
are issued from the RM) GUARANTEED containers, and given that GUARANTEED
containers do not stay in the scheduled state for long (actually, they are
there just momentarily), we thought it should be fine. But yes, there is a
small window where a client can ask and for the status and SCHEDULED can be
returned. Is it ok if for the fix, we check and return RUNNING to the client if
the container is GUARANTEED ?
> 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
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
