Usually this message means that the test was starting some process like a Spark master and it didn't ever start. The eventual error is "timeout". You have to try to dig in to the test and logs to catch the real reason.
On Sun, Jul 5, 2015 at 9:23 PM, SamRoberts <samueli.robe...@yahoo.com> wrote: > Also, it's not clear where to 10000 millisec timeout is coming from. Can > someone explain -- and if it's a legitimate timeout problem, where would one > set this timeout? > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/Futures-timed-out-after-10000-milliseconds-tp23622p23629.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org > For additional commands, e-mail: user-h...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
