[
https://issues.apache.org/jira/browse/HBASE-12986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-12986:
-----------------------------------
Assignee: Heng Chen (was: Andrew Purtell)
No progress from me, assigning to you [~chenheng]
Patch looks good, +1 from me
{quote}
As for the first comment, it sounds a great change, maybe we can do it in
another issue....
bq. We might also want to leave the current ExponentialClientBackoffPolicy as
is and introduce a new version of it that decouples the response to load
factors from contributions of load factor terms to the equation.
{quote}
Agreed, it's time now to do this, now that we have three factors that people
may want to mix in different ways, and potentially more, like system load based
etc.
> Compaction pressure based client pushback
> -----------------------------------------
>
> Key: HBASE-12986
> URL: https://issues.apache.org/jira/browse/HBASE-12986
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Heng Chen
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-12986.patch
>
>
> HBASE-8329 recently introduced on all branches {{double
> RegionServerServices#getCompactionPressure()}}, which returns a value greater
> than or equal to 0.0, and any value greater than 1.0 means we have exceeded
> the store file limit on some stores. It could be reasonable to send this
> value along in server load statistics (clamping max at 1.0), and consider it
> as an additional term in the ExponentialClientBackoffPolicy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
