You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2018/04/20 20:06:00 UTC

[jira] [Created] (HBASE-20468) RPC quota requests ineffective due to not counting multi-actions

Josh Elser created HBASE-20468:
----------------------------------

             Summary: RPC quota requests ineffective due to not counting multi-actions
                 Key: HBASE-20468
                 URL: https://issues.apache.org/jira/browse/HBASE-20468
             Project: HBase
          Issue Type: Bug
          Components: rpc
            Reporter: Josh Elser
            Assignee: Josh Elser
             Fix For: 2.1.0, 1.5.0, 1.3.3, 1.2.8, 1.4.4, 2.0.1


Was digging into a problem with [~ankit.singhal] where setting RPC quotas on number of requests wasn't having any effect on a multi-Get

Ankit did enough digging to find that this was because each RPC was being treated as one request instead of the number of requests contained within the RPC itself.

Thinking as an operator, this is a pretty ineffective control because a user could just craft their API usage easily to work around any kind of limits I want to set to control their impact on the system. TimeBasedLimiter is assuming that one call to the quota code can only count as one request which I think is just wrong.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)