[
https://issues.apache.org/jira/browse/HBASE-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898725#comment-13898725
]
Hadoop QA commented on HBASE-7849:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12628403/hbase-7849_v2.patch
against trunk revision .
ATTACHMENT ID: 12628403
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 hadoop1.1{color}. The patch compiles against the hadoop
1.1 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:red}-1 site{color}. The patch appears to cause mvn site goal to
fail.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-thrift.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8665//console
This message is automatically generated.
> 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
> 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)