[
https://issues.apache.org/jira/browse/HIVE-12650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15127492#comment-15127492
]
Rui Li commented on HIVE-12650:
-------------------------------
Thanks guys for your inputs. My understanding is that
{{hive.spark.client.server.connect.timeout}} is the timeout between RPC server
and client handshake. In {{RemoteDriver}}, RPC client is created before
SparkContext. And if {{spark.yarn.am.waitTime}} is the timeout waiting for
SparkContext to be created, maybe it won't help here. I mean we can try
increasing {{hive.spark.client.server.connect.timeout}}, but according to
something else.
BTW, is it possible the timeout is caused by the schedule delay within yarn? Is
the issue only encountered with yarn-cluster?
> Increase default value of hive.spark.client.server.connect.timeout to exceeds
> spark.yarn.am.waitTime
> ----------------------------------------------------------------------------------------------------
>
> Key: HIVE-12650
> URL: https://issues.apache.org/jira/browse/HIVE-12650
> Project: Hive
> Issue Type: Bug
> Affects Versions: 1.1.1, 1.2.1
> Reporter: JoneZhang
> Assignee: Xuefu Zhang
>
> I think hive.spark.client.server.connect.timeout should be set greater than
> spark.yarn.am.waitTime. The default value for
> spark.yarn.am.waitTime is 100s, and the default value for
> hive.spark.client.server.connect.timeout is 90s, which is not good. We can
> increase it to a larger value such as 120s.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
