hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12731) Heap occupancy based client pushback
Date Thu, 22 Jan 2015 18:50:35 GMT

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

Andrew Purtell commented on HBASE-12731:

bq.  do we want to pull the heap occupancy into a separate policy and then have a combining

I don't think so at this stage but as we build in more dimensions of load reporting over time
it's something we will eventually need to deal with. Right now it's pretty simple and the
calculation makes sense and is easy to understand. Let me open a doc issue to update the online
manual about this feature now that I'm thinking about it.

bq. java docs on the public static scale() method would be good,

Ok, let me first of all make it private. Will add javadoc too. Back in a sec. 

> Heap occupancy based client pushback
> ------------------------------------
>                 Key: HBASE-12731
>                 URL: https://issues.apache.org/jira/browse/HBASE-12731
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 0.98.10, 1.1.0
>         Attachments: HBASE-12731.patch, HBASE-12731.patch
> If the heap occupancy of a RegionServer is beyond a configurable high water mark (suggestions:
95%, 98%) then we should reject all user RPCs and only allow administrative RPCs until occupancy
has dropped below a configurable low water mark (suggestions: 92%). 
> Implement building on the HBASE-5162 changes.
> It might be expensive to check heap occupancy, in which case we can sample it periodically
with a chore and use the last known value in pushback calculations. 

This message was sent by Atlassian JIRA

View raw message