hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13098) HBase Connection Control
Date Thu, 26 Feb 2015 14:57:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338484#comment-14338484

Ashish Singhi commented on HBASE-13098:

bq. Please review current state of RPC and fold into your design what is missing. We already
bound inbound traffic. Point out what is wrong w/ our approach. Thanks.
[~saint.ack@gmail.com], thanks for your comment. There is nothing in our approach. I went
through HBASE-11598 and found that it limits the control only on few api's not all (correct
me If I am wrong here) and I did not find any other RPC connection controllers. So came up
with this.
May be I can relate this one with [~ndimiduk] idea on HBASE-13101.

> HBase Connection Control
> ------------------------
>                 Key: HBASE-13098
>                 URL: https://issues.apache.org/jira/browse/HBASE-13098
>             Project: HBase
>          Issue Type: New Feature
>          Components: security
>            Reporter: Ashish Singhi
>            Assignee: Ashish Singhi
>         Attachments: HBASE-13098.patch, HBase Connection Control.pdf
> It is desirable to set the limit on the number of client connections permitted to the
HBase server by controlling with certain system variables/parameters. Too many connections
to the HBase server imply too many queries and MR jobs running on HBase. This can slow down
the performance of the system and lead to denial of service. Hence such connections need to
be controlled. Using too many connections may just cause thrashing rather than get more useful
work done.
> This is kind off inspired from http://www.ebaytechblog.com/2014/08/21/quality-of-service-in-hadoop/#.VO2JXXyUe9y

This message was sent by Atlassian JIRA

View raw message