[
https://issues.apache.org/jira/browse/YARN-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15870096#comment-15870096
]
Jason Lowe commented on YARN-6177:
----------------------------------
The best effort setting was primarily targeting the scenario where the timeline
server is down and not wanting jobs to fail as a result. It wasn't intended to
mask jar conflicts like this.
Maybe I'm misunderstanding option #1 from above, but we should not be changing
the best-effort default value. That's an incompatible and surprising change.
When someone sets best-effort to true then they desire the timeline server to
work but don't want transient errors to block the job's progress. This case is
not a transient error -- the timeline client is never going to work with that
jar conflict in place. Therefore I agree with [~gtCarrera9] that we should not
mask this error. If it's common then I think we should check for it and
provide a useful error message stating the user needs to address the classpath
conflict or disable the timeline client, but the error should still be fatal.
> 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,
> YARN-6177.04.patch, YARN-6177.05.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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
