[
https://issues.apache.org/jira/browse/YARN-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069164#comment-16069164
]
Roni Burd commented on YARN-6753:
---------------------------------
I was wondering what people feel around exposing some of the internals to allow
debugging tools and other AMs to get insight into the NM. I understand that
there can be reluctance to take a code dependencies, but by using protobuf the
dependency should be weak. There are other internals I would like to expose
over time like, Working Directory, etc.
[~wangda] [~jianhe] , any thoughts? Do you have any recommendation what would
be a " kosher" way of doing this?
> 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]
