Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 20 May 2015 06:03:01 +0000 (UTC)
From: "Ashish Singhi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12777461.1424857018000.166287.1432101781099@Atlassian.JIRA>
In-Reply-To: <JIRA.12777461.1424857018000@Atlassian.JIRA>
References: <JIRA.12777461.1424857018000@Atlassian.JIRA>
 <JIRA.12777461.1424857018174@arcas>
Subject: [jira] [Resolved] (HBASE-13098) HBase Connection Control
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-13098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashish Singhi resolved HBASE-13098.
-----------------------------------
    Resolution: Not A Problem

Number of connection/requests to a table/namespace can be controlled using quota.

> 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
(v6.3.4#6332)