[
https://issues.apache.org/jira/browse/YARN-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070187#comment-16070187
]
Jason Lowe commented on YARN-6753:
----------------------------------
Technically adding LOCALIZING and LOCALIZED is going to break some clients.
They currently only expect NEW, RUNNING, and COMPLETE. As soon as we start
returning LOCALIZING/LOCALIZED instead of RUNNING that can break clients who
are not expecting the new value.
To be completely backwards compatible the request for container state needs to
include client version information so we know which enumerations the client
expects. If it is an older client then the NM can map the new states to the
older enums. For example, if a client asks for container state and doesn't
include any client version info then we know we need to map
LOCALIZED/LOCALIZING to RUNNING and EXIT_WITH_FAILURES to COMPLETE.
> Expose more ContainerImpl states from NM in ContainerStateProto
> ----------------------------------------------------------------
>
> Key: YARN-6753
> URL: https://issues.apache.org/jira/browse/YARN-6753
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Reporter: Roni Burd
> Priority: Minor
>
> The current NM protobuf definition exposes a subset of the NM internal state
> via ContainerStateProto.
> We are currently building tools that can use of more fine grain state like
> LOCALIZING, LOCALIZED, EXIT_WITH_FAILURES etc.
> The proposal is to add more internal states in the API.
> I'm not sure if this is considered an Incompatible change or not
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
