[
https://issues.apache.org/jira/browse/YARN-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856995#comment-15856995
]
Li Lu commented on YARN-5271:
-----------------------------
Thanks [~cheersyang].
bq. The fix here was trying to alleviate this pain, it prints a warning on
console and warns user timeline client could not be initialized because of
dependency issue, more user friendly.
The goad sounds reasonable but I don't think that justifies the behavior to
catch and swallow an Error. What we can do is to clearly document this behavior
as a known issue, *suggest* uses to *try* disable timeline services when seeing
this error, instead of directly assume the root cause of an error?
> ATS client doesn't work with Jersey 2 on the classpath
> ------------------------------------------------------
>
> Key: YARN-5271
> URL: https://issues.apache.org/jira/browse/YARN-5271
> Project: Hadoop YARN
> Issue Type: Bug
> Components: client, timelineserver
> Affects Versions: 2.7.2
> Reporter: Steve Loughran
> Assignee: Weiwei Yang
> Labels: oct16-medium
> Fix For: 2.8.0, 3.0.0-alpha2
>
> Attachments: YARN-5271.01.patch, YARN-5271.02.patch,
> YARN-5271.branch-2.01.patch, YARN-5271-branch-2.8.01.patch
>
>
> see SPARK-15343 : once Jersey 2 is on the CP, you can't instantiate a
> timeline client, *even if the server is an ATS1.5 server and publishing is
> via the FS*
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
