@Marcelo: Interesting - why would this manifest on the YARN-client side though (as Spark is the client to YARN in this case)? Spark as a client shouldn’t care about what auxiliary services are on the YARN cluster.
@Jesse: The change I wrote excludes all artifacts from the com.sun.jersey group. So to allow usage of the timeline service, we specifically need to find the thing that we don’t want to exclude and exclude everything but that from the YARN dependencies. I think the class that’s missing in this particular stack trace comes from com.sun.jersey:jersey-client. Refactoring the exclusions in pom.xml under hadoop-yarn-api to not exclude jersey-client should fix at least this. Again – we want to exclude all the other Jersey things that YARN is pulling in though, unless further errors indicate otherwise. In general I’m wary of having both Jersey 1 and Jersey 2 jars on the class path at all. However jersey-client looks relatively harmless since it does not bundle in JAX-RS classes, nor does it appear to have anything weird in its META-INF folder. -Matt Cheah On 5/9/16, 3:10 PM, "Marcelo Vanzin" <van...@cloudera.com> wrote: >Hi Jesse, > >On Mon, May 9, 2016 at 2:52 PM, Jesse F Chen <jfc...@us.ibm.com> wrote: >> Sean - thanks. definitely related to SPARK-12154. >> Is there a way to continue use Jersey 1 for existing working >>environment? > >The error you're getting is because of a third-party extension that >tries to talk to the YARN ATS; that's not part of upstream Spark, >although I believe it's part of HDP. So you may have to talk to >Hortonworks about that, or disable that extension in Spark 2.0 for the >moment. > > >-- >Marcelo --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
