[
https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046444#comment-16046444
]
Clay B. commented on HBASE-18023:
---------------------------------
Hi [~dharju], thanks for asking. I would suspect this is very specific to a
cluster's usage and the specific pathology one's seeking out. In our case I
think it happened to be 10's of thousands of writes. But I would imagine like
`hbase.ipc.warn.response.time` or `hbase.ipc.warn.response.size` this could be
tuned and left with a generic (or non-warning) default?
> 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: Josh Elser
> Priority: Minor
>
> 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)
