[
https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764579#comment-13764579
]
Zhijie Shen commented on YARN-978:
----------------------------------
{code}
+ @Private
+ @Unstable
+ public abstract void setDiagnostics(String diagnostics);
+
+ /**
+ * Get the <em>logs url</em> for the application attempt.
+ *
+ * @return <em>logs url</em> for the application attempt
+ */
+ @Public
+ @Unstable
+ public abstract String getLogsUrl();
+
{code}
Should it be the trackingUrl? LogUrl should be part of the container report.
Application attempt report has the Id of the AM container, which can be used to
retrieve the container report.
Then, put forward a another question. Shall we include some info (e.g., logUrl)
of the container report of the AM container into the application attempt
report, just as the application report has the info of the final application
attempt? Thoughts?
> [YARN-321] Adding ApplicationAttemptReport and Protobuf implementation
> ----------------------------------------------------------------------
>
> Key: YARN-978
> URL: https://issues.apache.org/jira/browse/YARN-978
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Mayank Bansal
> Assignee: Xuan Gong
> Fix For: YARN-321
>
> Attachments: YARN-978-1.patch, YARN-978.2.patch, YARN-978.3.patch,
> YARN-978.4.patch, YARN-978.5.patch, YARN-978.6.patch, YARN-978.7.patch
>
>
> We dont have ApplicationAttemptReport and Protobuf implementation.
> Adding that.
> Thanks,
> Mayank
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
