Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 20 Aug 2015 02:34:46 +0000 (UTC)
From: "Enis Soztutar (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12838268.1434483693000.114444.1440038086639@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=14704187#comment-14704187 ] 

Enis Soztutar commented on HBASE-13919:
---------------------------------------

bq. I'm going to start by documenting all of these (unless they are already), and then see whether we actually need so many option, or whether we can derive some settings from the others.
Documentation would be good. But, different operations (put, get or multi-get, coprocessor call, etc) respect different parameters for RPC timeout, operation timeout and retries depending on the code path (whether HTable or AP is used). 

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