[SPARK-20465] Throws a proper exception rather than ArrayIndexOutOfBoundsException when temp directories could not be got/created

• Type: Improvement
• Status: Resolved
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.0
• Component/s: Spark Core, Spark Submit
• Assignee: Hyukjin Kwon
• Reporter: Hyukjin Kwon
• Created: 26/Apr/17 04:50
• Updated: 12/Dec/22 17:51
• Resolved: 28/Apr/17 07:49

Description

If none of temp directories could not be created, it throws an ArrayIndexOutOfBoundsException as below:

./bin/spark-shell --conf spark.local.dir=/NONEXISTENT_DIR_ONE,/NONEXISTENT_DIR_TWO
17/04/26 13:11:06 ERROR Utils: Failed to create dir in /NONEXISTENT_DIR_ONE. Ignoring this directory.
17/04/26 13:11:06 ERROR Utils: Failed to create dir in /NONEXISTENT_DIR_TWO. Ignoring this directory.
Exception in thread "main" java.lang.ExceptionInInitializerError
	at org.apache.spark.repl.Main.main(Main.scala)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:497)
	at org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:756)
	at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:179)
	at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:204)
	at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:118)
	at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 0
	at org.apache.spark.util.Utils$.getLocalDir(Utils.scala:743)
	at org.apache.spark.repl.Main$$anonfun$1.apply(Main.scala:37)
	at org.apache.spark.repl.Main$$anonfun$1.apply(Main.scala:37)
	at scala.Option.getOrElse(Option.scala:121)
	at org.apache.spark.repl.Main$.<init>(Main.scala:37)
	at org.apache.spark.repl.Main$.<clinit>(Main.scala)
	... 10 more

It seems we should throw a proper exception with better message.

Issue Links

• links to: [Github] Pull Request #17768 (HyukjinKwon)