[
https://issues.apache.org/jira/browse/HBASE-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16249931#comment-16249931
]
Hadoop QA commented on HBASE-14756:
-----------------------------------
| (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 4s{color}
| {color:red} HBASE-14756 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.6.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HBASE-14756 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12770606/HBASE-14756.patch |
| Console output |
https://builds.apache.org/job/PreCommit-HBASE-Build/9771/console |
| Powered by | Apache Yetus 0.6.0 http://yetus.apache.org |
This message was automatically generated.
> Break out ClientBackoffPolicy factors into configurable and composable
> components
> ---------------------------------------------------------------------------------
>
> Key: HBASE-14756
> URL: https://issues.apache.org/jira/browse/HBASE-14756
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Heng Chen
> Attachments: HBASE-14756.patch
>
>
> Currently ExponentialClientBackoffPolicy evaluates three load parameters sent
> back in results from the server. The policy is fixed in implementation.
> Instead it should be possible to define the collection of considered load
> factors via configuration, and for each selected term parameterize how the
> load factor should contribute to the backoff calculation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
