[
https://issues.apache.org/jira/browse/YARN-6177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15869045#comment-15869045
]
Weiwei Yang commented on YARN-6177:
-----------------------------------
Hi [~gtCarrera9]
Yes, 2 approaches
# Set {{yarn.timeline-service.client.best-effort}} to {{true}} with this patch,
so yarn client doesn't treat such failure as a fatal error. Default value is
false, so user always hits the error with the prompted message at first time.
# Set {{yarn.timeine-service.enabled}} to {{false}} to disable timeline service
from client side config.
I was suggesting to use #1 because it literally explains the work around
better. Disable timeline service is a bit confusing because this property is
more like a server side config.
> 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: [email protected]
For additional commands, e-mail: [email protected]
