Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 14 Feb 2013 22:37:13 +0000 (UTC)
From: "Harsh J (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12632487.1360881397341.290710.1360881433029@arcas>
In-Reply-To: <JIRA.12632487.1360881397341@arcas>
References: <JIRA.12632487.1360881397341@arcas>
Subject: [jira] [Created] (HBASE-7849) Provide administrative limits around
 bulkloads of files into a single region
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Harsh J created HBASE-7849:
------------------------------

             Summary: Provide administrative limits around bulkloads of files into a single region
                 Key: HBASE-7849
                 URL: https://issues.apache.org/jira/browse/HBASE-7849
             Project: HBase
          Issue Type: Improvement
          Components: regionserver
            Reporter: Harsh J


Given the current mechanism, it is possible for users to flood a single region with 1k+ store files via the bulkload API and basically causes the region to become a flying dutchman - never getting assigned successfully again.

Ideally, an administrative limit could solve this. If the bulkload RPC call can check if the region already has X store files, then it can reject the request to add another and throw a failure at the client with an appropriate message.

This may be an intrusive change, but seems necessary in perfecting the gap between devs and ops in managing a HBase clusters. This would especially prevent abuse in form of unaware devs not pre-splitting tables before bulkloading things in. Currently, this leads to ops pain, as the devs think HBase has gone non-functional and begin complaining.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira