[
https://issues.apache.org/jira/browse/YARN-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15864950#comment-15864950
]
Li Lu commented on YARN-6177:
-----------------------------
One quick inquiry: are we catching every throwable and swallow them if
{{timelineServiceBestEffort}} is set to true? That sounds scary since we're
swallowing OutOfMemoryError, etc...
I think we should limit the range of {{timelineServiceBestEffort}} to
exceptions, but we still preserve the program's behavior on errors. Meanwhile,
we can improve the output message if we hit {{NoClassDefFoundError}} to hint
users to disable timeline service?
> Yarn client should exit with an informative error message if an incompatible
> Jersey library is used at client
> -------------------------------------------------------------------------------------------------------------
>
> Key: YARN-6177
> URL: https://issues.apache.org/jira/browse/YARN-6177
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.8.0, 3.0.0-alpha2
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Attachments: spark2-job-output-after-besteffort.out,
> spark2-job-output-after.out, spark2-job-output-before.out,
> YARN-6177.01.patch, YARN-6177.02.patch, YARN-6177.03.patch
>
>
> Per discussion in YARN-5271, lets provide an error message to suggest user to
> disable timeline service instead of disabling for them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
