[ https://issues.apache.org/jira/browse/YARN-7248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183654#comment-16183654 ]
Junping Du commented on YARN-7248: ---------------------------------- I think we should fix this in 3.0-beta also given rolling upgrade from 2.x is the goal. CC [~andrew.wang]. > 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-7248.002.patch, > YARN-7248.003.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 (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org