You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Jimmy Xiang (JIRA)" <ji...@apache.org> on 2014/02/11 20:42:33 UTC
[jira] [Assigned] (HBASE-7849) Provide administrative limits around
bulkloads of files into a single region
[ https://issues.apache.org/jira/browse/HBASE-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jimmy Xiang reassigned HBASE-7849:
----------------------------------
Assignee: Jimmy Xiang
> 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
> Assignee: Jimmy Xiang
>
> Given the current mechanism, it is possible for users to flood a single region with 1k+ store files via the bulkload API and basically cause 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 was sent by Atlassian JIRA
(v6.1.5#6160)