hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heng Chen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12986) Compaction pressure based client pushback
Date Mon, 26 Oct 2015 04:16:27 GMT

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

Heng Chen commented on HBASE-12986:
-----------------------------------

Any progress?  
I make a simple patch. :)   

{quote}
(clamping max at 1.0)
{quote}
Currently, {{compactionPressure}} >= 0,  as comments, if {{compactionPressure}}>=1,
it means heavy compaction pressure.
So i just set it to be 1 if it greater than 1.


As for the first comment,  it sounds a great change, maybe we can do it in another issue....
{quote}
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}

> 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: Andrew Purtell
>             Fix For: 2.0.0, 1.3.0
>
>
> 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)

Mime
View raw message