[
https://issues.apache.org/jira/browse/YARN-5271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15576247#comment-15576247
]
Jo Desmet edited comment on YARN-5271 at 10/14/16 7:23 PM:
-----------------------------------------------------------
Note that such tight coupling should not be required, not so that we have that
library dependency between spark and Yarn. The idea of Jersey is exactly to
avoid this type of tight coupling between two application frameworks. I think
it is still a huge drawback of not having the History Server up. I think it is
1./ Spark's job to have enough decoupling in place; 2./ Yarn to evolve fast
enough, being able to use latest libraries and benefit from added features and
improvements. That being said, most likely this fix is probably a good first
step.
was (Author: [email protected]):
Note that such tight coupling should not be required, not so that we have that
library dependency between spark and Yarn. The idea of Jersey is exactly to
avoid this type of tight coupling between two application frameworks. I think
it is still a huge drawback of not having the History Server up. I think it is
1./ Spark's job to have enough decoupling in place; 2./ Yarn to evolve fast
enough, being able to use latest libraries and benefit from added features and
improvements.
> 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
> Attachments: YARN-5271.01.patch, YARN-5271.branch-2.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.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
