[
https://issues.apache.org/jira/browse/HBASE-12731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14288130#comment-14288130
]
Hadoop QA commented on HBASE-12731:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12693977/HBASE-12731-0.98.patch
against master branch at commit 319f9bb7918af8cfe7e65f97b654f37f0d5983f3.
ATTACHMENT ID: 12693977
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 12 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/12557//console
This message is automatically generated.
> 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-0.98.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)
