You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Brock Noland (JIRA)" <ji...@apache.org> on 2014/05/28 23:43:04 UTC
[jira] [Updated] (HIVE-7140) Bump default
hive.metastore.client.socket.timeout to 5 minutes
[ https://issues.apache.org/jira/browse/HIVE-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brock Noland updated HIVE-7140:
-------------------------------
Description:
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.
was:
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
> 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
> Reporter: Brock Noland
>
> 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)