[
https://issues.apache.org/jira/browse/HIVE-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14021480#comment-14021480
]
Lefty Leverenz commented on HIVE-7140:
--------------------------------------
When release 0.14 comes along, this new default value for
*hive.metastore.client.socket.timeout* needs to be documented in
hive-default.xml.template (or in the description to be included in
HiveConf.java when HIVE-6037 gets committed). I've added a comment to
HIVE-6586 which tracks parameter changes for HIVE-6037.
It also needs to go in the wiki with release information:
* [Configuration Properties: hive.metastore.client.socket.timeout |
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.metastore.client.socket.timeout]
For the record, the new default is 600 seconds so that's 10 minutes, not 5
minutes as stated in this ticket's title and first comment.
> Bump default hive.metastore.client.socket.timeout to 5 minutes
> --------------------------------------------------------------
>
> Key: HIVE-7140
> URL: https://issues.apache.org/jira/browse/HIVE-7140
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 0.10.0, 0.12.0, 0.13.0
> Reporter: Brock Noland
> Assignee: Brock Noland
> Fix For: 0.14.0
>
> Attachments: HIVE-7140.patch
>
>
> The issue is that OOTB clients often face timeouts when using HMS since many
> operations in the HMS completes are long running (e.g. many operations on a
> table with many partitions). A few supporting pieces of information:
> * The default value of hive.metastore.client.socket.timeout is 20 seconds.
> * Since the timeout is client only, the server happy continues doing the
> requested work
> * Clients retry after a small delay to perform the requested work again,
> often while the server is still trying to complete the original request
> * A few tests have actually increased this value in order to pass reliably.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
