umm, i am not sure if I got this fully. It is a design decision to not have context.stop() right after awaitTermination throws exception?
So, the ideology is that if after n tries (default 4) a task fails, the spark should fail fast and let user know? Is this correct? As you mentioned there are many error classes and as the chances of getting an exception are quite high. If the above ideology is correct then it makes it really hard to keep the job up and running all the time especially streaming cases. -- Sent from: http://apache-spark-user-list.1001560.n3.nabble.com/ --------------------------------------------------------------------- To unsubscribe e-mail: user-unsubscr...@spark.apache.org
