[
https://issues.apache.org/jira/browse/YARN-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503704#comment-16503704
]
Vrushali C commented on YARN-8155:
----------------------------------
Thanks for the patch [~abmodi]!
A few questions.
In NMTimelinePublisher, do we think it might be a good idea to log the
exception in debug mode as is being done in TimelineServiceV2Publisher? On the
NM side, in case of issues, it may be good idea to see the stack trace?
In TimelineServiceV2Publisher, looks like we are updating Exception to
IOException. So I am wondering what would happen if putEntity might throw some
other exception than IOException?
Similarly for TimelineCollectorWebService#putEntities on L185, L237 and L254.
> Improve the logging in NMTimelinePublisher and TimelineCollectorWebService
> --------------------------------------------------------------------------
>
> Key: YARN-8155
> URL: https://issues.apache.org/jira/browse/YARN-8155
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Rohith Sharma K S
> Assignee: Abhishek Modi
> Priority: Major
> Attachments: YARN-8155.001.patch, YARN-8155.002.patch,
> YARN-8155.003.patch, YARN-8155.004.patch
>
>
> We see that NM logs are filled with larger stack trace of NotFoundException
> if collector is removed from one of the NM and other NMs are still publishing
> the entities.
>
> This Jira is to improve the logging in NM so that we log with informative
> message.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
