[
https://issues.apache.org/jira/browse/YARN-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766572#comment-13766572
]
Xuan Gong commented on YARN-978:
--------------------------------
bq. I'm fine with remove it, but trackingUrl is on web UI according to the
latest patches in YARN-954 and YARN-1023. If it is to be removed, we should
leave note there.
Yes, We might still need trackingUrl. Originally, I though the trackingUrl will
be set as null, so we might not need it. But I checked code again. Actually,
this is from the ApplicationMaster
{code}
resourceManager.unregisterApplicationMaster(appStatus, appMessage, null);
{code}.
I am thinking since this applicationMaster can be re-wrote or provided by the
client, this will be changed, too. (At least from MRApplicationMaster, the
trackUrl is set as non-null). So, we can add trackUrl to the
applicationAttemptReport.
And I agree that the logUrl should go to the containerReport.
> [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
