reminder: this is happening thursday morning.
On Wed, May 4, 2016 at 11:38 AM, shane knapp wrote:
> there's a security update coming out for jenkins next week, and i'm
> going to install the update first thing thursday morning.
>
> i'll send out another reminder early next
On Mon, May 9, 2016 at 3:34 PM, Matt Cheah wrote:
> @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.
The
@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
Hi Jesse,
On Mon, May 9, 2016 at 2:52 PM, Jesse F Chen 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 reason I ask how you're running is that YARN itself should have the
classes that YARN needs, and should be on your classpath. That's why it's
not in Spark.
There still could be a subtler problem. The best way to trouble shoot, if
you want to act on it now, is to have a look at the exclusions
Sean - thanks. definitely related to SPARK-12154.
Is there a way to continue use Jersey 1 for existing working environment?
Or, what's the best way to patch up existing Jersey 1 environment to Jersey
2?
This does break all of our Spark jobs running Spark 2.0 on YARN.
Hm, this may be related to updating to Jersey 2, which happened 4 days ago:
https://issues.apache.org/jira/browse/SPARK-12154
That is a Jersey 1 class that's missing. How are you building and running
Spark?
I think the theory was that Jersey 1 would still be supplied at runtime. We
may have to