Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Sun, 5 Jul 2015 16:08:04 +0000 (UTC)
From: "Anil Gupta (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12838268.1434483693000.100814.1436112484839@Atlassian.JIRA>
In-Reply-To: <JIRA.12838268.1434483693000@Atlassian.JIRA>
References: <JIRA.12838268.1434483693000@Atlassian.JIRA>
 <JIRA.12838268.1434483693242@arcas>
Subject: [jira] [Commented] (HBASE-13919) Rationalize Client Timeout
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-13919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614304#comment-14614304 ] 

Anil Gupta commented on HBASE-13919:
------------------------------------

 I think, we should break down these timeout properties in 2 categories. 
#1) Connecting to cluster: This currently timeouts in 20 minutes. I think this should timeout in not more than 1-2 minutes. I dont think anyone has patience to wait 20 minutes for a NoSql connection to fail.
#2) Scan, Get, Put timeouts

> Rationalize Client Timeout
> --------------------------
>
>                 Key: HBASE-13919
>                 URL: https://issues.apache.org/jira/browse/HBASE-13919
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: Lars Hofhansl
>
> There are current many setting that influence how/when an HBase client times out.
> This is hard to configure, hard to understand, and badly documented.
> Instead there should as few tweaks as needed, and their setting should make sense.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)