[
https://issues.apache.org/jira/browse/HIVE-9395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14282468#comment-14282468
]
Chengxiang Li commented on HIVE-9395:
-------------------------------------
>From the abstract level, job status should just wrap the job/stage status, and
>monitor would decide when to timeout. And in current implementation, we indeed
>need a timeout in monitor to break the monitor loop while failed to get job
>state, SparkJobStatus does know more information about job state, but I think
>monitor does not need extra information to timeout, I mean when monitor can
>not get job state in timeout interval, something definitely goes wrong during
>job submission, job monitor should timeout for use experience.
> 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)
