You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Phil Yang (JIRA)" <ji...@apache.org> on 2016/07/27 11:30:20 UTC
[jira] [Updated] (HBASE-16291) Explain the correct semantic of
hbase.client.retries.number in doc
[ https://issues.apache.org/jira/browse/HBASE-16291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Yang updated HBASE-16291:
------------------------------
Affects Version/s: 2.0.0
1.1.5
1.2.2
0.98.20
> Explain the correct semantic of hbase.client.retries.number in doc
> ------------------------------------------------------------------
>
> Key: HBASE-16291
> URL: https://issues.apache.org/jira/browse/HBASE-16291
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.0.0, 1.1.5, 1.2.2, 0.98.20
> Reporter: Phil Yang
> Assignee: Phil Yang
>
> In hbase-default.xml (and also in HBase Book), the description of hbase.client.retries.number is:
> {quote}
> Maximum retries. Used as maximum for all retryable operations such as the getting of a cell's value, starting a row update, etc. Retry interval is a rough function based on hbase.client.pause. At first we retry at this interval but then with backoff, we pretty quickly reach retrying every ten seconds. See HConstants#RETRY_BACKOFF for how the backup ramps up. Change this setting and hbase.client.pause to suit your workload.
> {quote}
> However, the semantic of this conf is confusing and different in various branches. After HBASE-14521, in master it means "the number of RETRIES", but in all the other branches it still means "the number of TRIES".
> So I think we need make the doc clearly and tell users what it is in 0.98/1.x and what it will be from 2.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)