[
https://issues.apache.org/jira/browse/HBASE-18023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated HBASE-18023:
-------------------------------
Release Note: HBASE-18023 introduces a warning message in the RegionServer
log when an RPC is received from a client that has more than 5000 "actions"
(where an "action" is a collection of mutations for a specific row) in a single
RPC. Misbehaving clients who send large RPCs to RegionServers can be malicious,
causing temporary pauses via garbage collection or denial of service via
crashes. The threshold of 5000 actions per RPC is defined by the property
"hbase.rpc.rows.warning.threshold" in hbase-site.xml.
> 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
> Fix For: 2.0.0, 3.0.0, 1.4.0, 1.3.2
>
> Attachments: HBASE-18023.addendum.patch,
> HBASE-18023-branch-1.3.patch, HBASE-18023-branch-1.patch,
> HBASE-18023.master.001.patch, HBASE-18023.master.002.patch,
> HBASE-18023.master.003.patch, HBASE-18023.master.004.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)
