[
https://issues.apache.org/jira/browse/SPARK-18241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hyukjin Kwon updated SPARK-18241:
---------------------------------
Labels: bulk-closed (was: )
> If Spark Launcher fails to startApplication then handle's state does not
> change
> -------------------------------------------------------------------------------
>
> Key: SPARK-18241
> URL: https://issues.apache.org/jira/browse/SPARK-18241
> Project: Spark
> Issue Type: Bug
> Components: Spark Submit
> Affects Versions: 2.0.0
> Reporter: Aseem Bansal
> Priority: Major
> Labels: bulk-closed
>
> I am using Spark 2.0.0. I am using
> https://spark.apache.org/docs/2.0.0/api/java/org/apache/spark/launcher/SparkLauncher.html
> to submit my job.
> If there is a failure after launcher's startapplication has been called but
> before the spark job has actually started (i.e. in starting the spark process
> that submits the job itself) there is
> * no exception in the main thread that is submitting the job
> * no exception in the job as it has not started
> * no state change of the launcher
> * the exception is logged in the error stream on the default logger name that
> spark produces using the Job's main class.
> Basically, it is not possible to catch an exception if it happens during that
> time. The easiest way to reproduce it is to delete the JAR file or use an
> invalid spark home while launching the job using sparkLauncher.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]