[
https://issues.apache.org/jira/browse/HIVE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282303#comment-14282303
]
Rui Li commented on HIVE-9395:
------------------------------
Any reason why we want to move the timeout to SparkJobMonitor level? Because it
seems SparkJobStatus has more knowledge about the job progress, e.g. whether
the job ID has been received, whether the remote spark context returns a proper
SparkJobInfo for a job ID.
> Make WAIT_SUBMISSION_TIMEOUT configuable and check timeout in SparkJobMonitor
> level.[Spark Branch]
> --------------------------------------------------------------------------------------------------
>
> Key: HIVE-9395
> URL: https://issues.apache.org/jira/browse/HIVE-9395
> Project: Hive
> Issue Type: Sub-task
> Components: Spark
> Reporter: Chengxiang Li
> Assignee: Chengxiang Li
> Labels: Spark-M5
> Attachments: HIVE-9395.1-spark.patch
>
>
> SparkJobMonitor may hang if job state return null all the times, we should
> move the timeout check here to avoid it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
