[
https://issues.apache.org/jira/browse/HIVE-12046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947172#comment-14947172
]
Jimmy Xiang commented on HIVE-12046:
------------------------------------
For getDefaultParallelism() and getExecutorCount(), connection drop doesn't
break the query. We log a warning in this case. That's why I didn't touch them.
Right, the remote client can become bad right after the isActive() check. User
will get an exception in this case. We can enhance the error message and ask
the user to re-try the query, which should be more convenient than logging out
and in again.
> Re-create spark client if connection is dropped
> -----------------------------------------------
>
> Key: HIVE-12046
> URL: https://issues.apache.org/jira/browse/HIVE-12046
> Project: Hive
> Issue Type: Bug
> Components: Spark
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 1.3.0, 2.0.0
>
> Attachments: HIVE-12046.1.patch
>
>
> Currently, if the connection to the spark cluster is dropped, the spark
> client will stay in a bad state. A new Hive session is needed to re-establish
> the connection. It is better to auto reconnect in this case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
