Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 20FCF175E7 for ; Wed, 25 Feb 2015 23:02:07 +0000 (UTC) Received: (qmail 53213 invoked by uid 500); 25 Feb 2015 23:02:06 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 53174 invoked by uid 500); 25 Feb 2015 23:02:06 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 53158 invoked by uid 99); 25 Feb 2015 23:02:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 23:02:06 +0000 Date: Wed, 25 Feb 2015 23:02:06 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-13098) HBase Connection Control MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337409#comment-14337409 ] Andrew Purtell commented on HBASE-13098: ---------------------------------------- We already have a hierarchy of RPC connection controllers descending from the {{RpcController}} interface, pluggable via {{RpcControllerFactories}}, and in use by client apps such as Apache Phoenix. Can this be implemented within that framework? I skimmed the patch and the {{ConnectionControl}} concept seems similar in some respects (controlling RPC) but more limited in others (can only accept or reject connections). > HBase Connection Control > ------------------------ > > Key: HBASE-13098 > URL: https://issues.apache.org/jira/browse/HBASE-13098 > Project: HBase > Issue Type: New Feature > Components: security > Affects Versions: 0.98.10 > Reporter: Ashish Singhi > Assignee: Ashish Singhi > Fix For: 2.0.0, 1.1.0, 0.98.11 > > 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 (v6.3.4#6332)