[
https://issues.apache.org/jira/browse/YARN-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955513#comment-13955513
]
Zhijie Shen commented on YARN-808:
----------------------------------
IMHO, it's a different issue. The "N/A" string is not just restricted in host,
but diagnostics, tracking url and etc, and not in ApplicationReport, but in
ApplicationAttemptReport and ContainerReport.
I think the good thing is to decouple the data and the display. While these
string fields should keep null or empty for those programmatically get the
reports to easily validate them, while webUI and CLI, who ware actually the
consumers of the reports, should check whether these fields are null or empty,
and display "N/A" when necessary.
> ApplicationReport does not clearly tell that the attempt is running or not
> --------------------------------------------------------------------------
>
> Key: YARN-808
> URL: https://issues.apache.org/jira/browse/YARN-808
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.1.0-beta
> Reporter: Bikas Saha
> Assignee: Xuan Gong
> Attachments: YARN-808.1.patch
>
>
> When an app attempt fails and is being retried, ApplicationReport immediately
> gives the new attemptId and non-null values of host etc. There is no way for
> clients to know that the attempt is running other than connecting to it and
> timing out on invalid host. Solution would be to expose the attempt state or
> return a null value for host instead of "N/A"
--
This message was sent by Atlassian JIRA
(v6.2#6252)
