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

Yu Li commented on HBASE-16291:
-------------------------------

Thanks for the write up [~yangzhe1991].

One thing to emphasize here is that in 0.9x/1.x the semantic diverges in 
different functions (Please refer to HBASE-14521 for more details), so I'm 
afraid it's not precise to say in 0.9x/1.x it means "the number of TRIES".

Reason of HBASE-14521 not committed into master branch (quote of [~nkeywal]'s 
comments there):
bq. Committed to master. I didn't commit to 1.x branch because it's a behavior 
change...

> 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
>         Attachments: HBASE-16291-v1.patch
>
>
> 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 clear 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)

Reply via email to