[
https://issues.apache.org/jira/browse/HBASE-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900049#comment-13900049
]
Hudson commented on HBASE-7849:
-------------------------------
FAILURE: Integrated in HBase-0.98 #154 (See
[https://builds.apache.org/job/HBase-0.98/154/])
HBASE-7849 Provide administrative limits around bulkloads of files into a
single region (jxiang: rev 1567738)
*
/hbase/branches/0.98/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java
*
/hbase/branches/0.98/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java
*
/hbase/branches/0.98/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestSecureLoadIncrementalHFiles.java
> 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
> Fix For: 0.98.0, 0.98.1, 0.99.0
>
> Attachments: hbase-7849.patch, hbase-7849_v2.patch
>
>
> 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)
