[
https://issues.apache.org/jira/browse/YARN-1123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793962#comment-13793962
]
Zhijie Shen commented on YARN-1123:
-----------------------------------
We should not include ContainerStatus, which contains containerId, diagnostics,
...
{code}
+ /**
+ * Get the final <code>ContainerStatus</code> of the container.
+ *
+ * @return final <code>ContainerStatus</code> of the container.
+ */
+ @Public
+ @Unstable
+ public abstract ContainerStatus getContainerStatus();
+
+ @Public
+ @Unstable
+ public abstract void setContainerStatus(ContainerStatus ContainerStatus);
{code}
ContainerHistoryData contains the record, which is ContainerState. Think about
it again: ContainerState only has three enums: NEW, RUNNING, COMPLETE. All the
ContainerHistoryData should be COMPLETE, therefore, this field will be
meaningless, unless we define more final states in ContainerState, However, I'm
not sure whether we intentionally let ContainerState only have one final state.
The other choice is to use container exit code instead. Thoughts?
> [YARN-321] Adding ContainerReport and Protobuf implementation
> -------------------------------------------------------------
>
> Key: YARN-1123
> URL: https://issues.apache.org/jira/browse/YARN-1123
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Zhijie Shen
> Assignee: Mayank Bansal
> Attachments: YARN-1123-1.patch, YARN-1123-2.patch
>
>
> Like YARN-978, we need some client-oriented class to expose the container
> history info. Neither Container nor RMContainer is the right one.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
