Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 11 Jan 2017 09:23:58 +0000 (UTC)
From: "Yu Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13033655.1484126626000.707250.1484126638329@Atlassian.JIRA>
In-Reply-To: <JIRA.13033655.1484126626000@Atlassian.JIRA>
References: <JIRA.13033655.1484126626000@Atlassian.JIRA> <JIRA.13033655.1484126626762@arcas>
Subject: [jira] [Created] (HBASE-17449) Add explicit document on different
 timeout settings
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 11 Jan 2017 09:24:00 -0000

Yu Li created HBASE-17449:
-----------------------------

             Summary: Add explicit document on different timeout settings
                 Key: HBASE-17449
                 URL: https://issues.apache.org/jira/browse/HBASE-17449
             Project: HBase
          Issue Type: Improvement
          Components: documentation
            Reporter: Yu Li


Currently we have more than one timeout settings, mainly includes:
* hbase.rpc.timeout
* hbase.client.operation.timeout
* hbase.client.scanner.timeout.period

And in latest branch-1 or master branch code, we will have two other properties:
* hbase.rpc.read.timeout
* hbase.rpc.write.timeout

However, in current refguid we don't have explicit instruction on the difference of these timeout settings (there're explanations for each property, but no instruction on when to use which)

In my understanding, for RPC layer timeout, or say each rpc call:
* Scan (openScanner/next): controlled by hbase.client.scanner.timeout.period
* Other operations:
   1. For released versions: controlled by hbase.rpc.timeout
   2. For 1.4+ versions: read operation controlled by hbase.rpc.read.timeout, write operation controlled by hbase.rpc.write.timeout, or hbase.rpc.timeout if the previous two are not set.

And hbase.client.operation.timeout is a higher-level control counting retry in, or say the overall control for one user call.

After this JIRA, I hope when users ask questions like "What settings I should use if I don't want to wait for more than 1 second for a single put/get/scan.next call", we could give a neat answer.


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