[
https://issues.apache.org/jira/browse/HBASE-7849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13898483#comment-13898483
]
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/12628345/hbase-7849.patch
against trunk revision .
ATTACHMENT ID: 12628345
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:red}-1 hadoop1.0{color}. The patch failed to compile against the
hadoop 1.0 profile.
Here is snippet of errors:
{code}[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hbase-server: Compilation failure: Compilation
failure:
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java:[50,29]
cannot find symbol
[ERROR] symbol : class GenericTestUtils
[ERROR] location: package org.apache.hadoop.test
[ERROR]
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFiles.java:[384,6]
cannot find symbol
[ERROR] symbol : variable GenericTestUtils
--
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) on project hbase-server: Compilation failure
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
--
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation
failure
at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:729)
at
org.apache.maven.plugin.TestCompilerMojo.execute(TestCompilerMojo.java:161)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more{code}
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/8663//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
>
>
> 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)
