[
https://issues.apache.org/jira/browse/HBASE-12731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14285014#comment-14285014
]
Andrew Purtell commented on HBASE-12731:
----------------------------------------
Oh, and HeapMemoryManager was/is responsible for autotuning if that feature is
enabled. If we are over the heap occupancy low water mark, we enter an alarm
state that temporarily disables autotuning until we drop below the watermark,
which seems very prudent.
> 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
> Attachments: 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)
