[
https://issues.apache.org/jira/browse/YARN-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070876#comment-16070876
]
Jian He commented on YARN-6753:
-------------------------------
Yep, I kinda prefer working on the existing class. Since the container state
is also used by RM for its own logic e.g RMNodeImpl#handleContainerStatus,
similar kind of mapping needs to be done there also.
On a related note, while working on YARN-1503, I also thought to expose the
state of whether localization failed or succeeded. But there I need a more
sophisticated localization status per resource, though we probably also need a
limit to limit the number resources object returned, otherwise, it could make
the getContainerStatus heavy.
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
