[
https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16058704#comment-16058704
]
Josh Elser commented on HBASE-18023:
------------------------------------
+1 Thanks for the updates. One final thing -- looks like I missed the changes
to
hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestHRegion.java
that are without consequence.
Let's race: I'll commit this tomorrow when I get a chance. If you can get a v4
up before then, I'll use that. Otherwise, I'll just commit your patch,
reverting the changes to TestHRegion.java before pushing ;)
> Log multi-* requests for more than threshold number of rows
> -----------------------------------------------------------
>
> Key: HBASE-18023
> URL: https://issues.apache.org/jira/browse/HBASE-18023
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Reporter: Clay B.
> Assignee: David Harju
> Priority: Minor
> Attachments: HBASE-18023.master.001.patch,
> HBASE-18023.master.002.patch, HBASE-18023.master.003.patch
>
>
> Today, if a user happens to do something like a large multi-put, they can get
> through request throttling (e.g. it is one request) but still crash a region
> server with a garbage storm. We have seen regionservers hit this issue and it
> is silent and deadly. The RS will report nothing more than a mysterious
> garbage collection and exit out.
> Ideally, we could report a large multi-* request before starting it, in case
> it happens to be deadly. Knowing the client, user and how many rows are
> affected would be a good start to tracking down painful users.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
