Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Wed, 28 May 2014 21:45:03 +0000 (UTC)
From: "Brock Noland (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12717144.1401313124915.34399.1401313503389@arcas>
In-Reply-To: <JIRA.12717144.1401313124915@arcas>
References: <JIRA.12717144.1401313124915@arcas>
Subject: [jira] [Updated] (HIVE-7140) Bump default
 hive.metastore.client.socket.timeout to 5 minutes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brock Noland updated HIVE-7140:
-------------------------------

    Attachment: HIVE-7140.patch

> 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
>         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)