You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Roni Burd (JIRA)" <ji...@apache.org> on 2017/07/01 01:11:00 UTC
[jira] [Commented] (YARN-6753) Expose more ContainerImpl states
from NM in ContainerStateProto
[ https://issues.apache.org/jira/browse/YARN-6753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070923#comment-16070923 ]
Roni Burd commented on YARN-6753:
---------------------------------
ok, so I'm hearing the consensus to be add a version number, and hide the logic in the clients. Default values arae set via protobuf and clients are unaware of the change.
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org