Skip to content
This repository has been archived by the owner on Feb 3, 2021. It is now read-only.

Cannot access wasbs filesystem from submitted job #366

Closed
emlyn opened this issue Feb 2, 2018 · 1 comment
Closed

Cannot access wasbs filesystem from submitted job #366

emlyn opened this issue Feb 2, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@emlyn
Copy link
Contributor

emlyn commented Feb 2, 2018

When I run an application via job submission, it looks like the azure storage jars are not added to the classpath (I see java.io.IOException: No FileSystem for scheme: wasbs). I've tried adding them to the application's jars: key in job.yaml, but this doesn't help.
In the log output I also see:

Warning: Local jar /home/spark-current/jars/azure-storage-2.0.0.jar does not exist, skipping.
Warning: Local jar /home/spark-current/jars/hadoop-azure-2.7.3.jar does not exist, skipping.
Warning: Local jar /home/spark-current/jars/azure-data-lake-store-sdk-2.2.3.jar does not exist, skipping.

Followed by:

java.io.FileNotFoundException: Jar /home/spark-current/jars/azure-storage-2.0.0.jar not found
	at org.apache.spark.SparkContext.addJarFile$1(SparkContext.scala:1807)
	at org.apache.spark.SparkContext.addJar(SparkContext.scala:1833)
	at org.apache.spark.SparkContext$$anonfun$12.apply(SparkContext.scala:466)
	at org.apache.spark.SparkContext$$anonfun$12.apply(SparkContext.scala:466)
	at scala.collection.immutable.List.foreach(List.scala:381)
	at org.apache.spark.SparkContext.<init>(SparkContext.scala:466)
	at org.apache.spark.SparkContext$.getOrCreate(SparkContext.scala:2509)
	at org.apache.spark.sql.SparkSession$Builder$$anonfun$6.apply(SparkSession.scala:909)
	at org.apache.spark.sql.SparkSession$Builder$$anonfun$6.apply(SparkSession.scala:901)
	at scala.Option.getOrElse(Option.scala:121)
	at org.apache.spark.sql.SparkSession$Builder.getOrCreate(SparkSession.scala:901)

And similar for hadoop-azure-2.7.3.jar, azure-data-lake-store-sdk-2.2.3.jar.
Do I need to do something in the config to make this work, or is it a bug?

@jafreck
Copy link
Member

jafreck commented Feb 2, 2018

I'm investigating this issue. You should not need to do anything in the config. This is likely a bug.

@jafreck jafreck added the bug label Feb 2, 2018
@jafreck jafreck self-assigned this Feb 2, 2018
@jafreck jafreck added this to the v0.5.2 milestone Feb 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants