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] [Updated] (HBASE-12731) Heap occupancy based client pushback
Date Thu, 05 Feb 2015 22:01:36 GMT

     [ https://issues.apache.org/jira/browse/HBASE-12731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell updated HBASE-12731:
-----------------------------------
    Release Note: This feature incorporates reported regionserver heap occupancy in the (optional)
client pushback calculations. If client pushback is enabled, the exponential backoff policy
will take heap occupancy into account, should it exceed "hbase.heap.occupancy.low_water_mark"
percentage of the heap (default 0.95). Once above the low water mark, heap occupancy is an
additional factor scaling from 0.1 up to 1.0 at "hbase.heap.occupancy.high_water_mark" (default
0.98). At or above the high water mark the client will use the maximum configured backoff.

> 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: 1.0.0, 2.0.0, 0.98.10, 1.1.0
>
>         Attachments: HBASE-12731-0.98.patch, HBASE-12731-0.98.patch, HBASE-12731.patch,
HBASE-12731.patch, 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
(v6.3.4#6332)

Mime
View raw message