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

HBase QA commented on HBASE-16291:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  9s{color} 
| {color:red} HBASE-16291 does not apply to master. Rebase required? Wrong 
Branch? See 
https://yetus.apache.org/documentation/in-progress/precommit-patchnames for 
help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-16291 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12820417/HBASE-16291-v1.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/403/console |
| Powered by | Apache Yetus 0.9.0 http://yetus.apache.org |


This message was automatically generated.



> 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: 1.1.5, 1.2.2, 0.98.20, 2.0.0
>            Reporter: Phil Yang
>            Assignee: Phil Yang
>            Priority: Major
>         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
(v7.6.3#76005)

Reply via email to