[
https://issues.apache.org/jira/browse/HBASE-13699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14546484#comment-14546484
]
Hadoop QA commented on HBASE-13699:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12733270/HBASE-13699.patch
against master branch at commit 88f0f421c3330f4ba914ecf89d8d2afe78cacbc4.
ATTACHMENT ID: 12733270
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.1 2.5.2 2.6.0)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ Disable a replication relationship. HBase will no longer send edits to
that peer cluster, but it still keeps track of all the new WALs that it will
need to replicate if and when it is re-enabled.
+ Enable the table replication switch for all it's column families. If the
table is not found in the destination cluster then it will create one with the
same name and column families.
+hbase> set_quota TYPE => THROTTLE, USER => 'u1', LIMIT => '10req/sec'
# a per-user request limit
+hbase> set_quota TYPE => THROTTLE, USER => 'u1', LIMIT => '10M/sec'
# a per-user size limit
+hbase> set_quota TYPE => THROTTLE, USER => 'u1', TABLE => 't2', LIMIT =>
'5K/min' # a per-user size limit on a table
+hbase> set_quota TYPE => THROTTLE, USER => 'u1', NAMESPACE => 'ns2', LIMIT =>
NONE # removing a per-namespace request limit
+hbase> set_quota TYPE => THROTTLE, NAMESPACE => 'ns1', LIMIT => '10req/sec'
# a per-namespace request limit
+hbase> set_quota TYPE => THROTTLE, TABLE => 't1', LIMIT => '10M/sec'
# a per-table size limit
+hbase> set_quota TYPE => THROTTLE, USER => 'u1', LIMIT => NONE
# removing a per-user limit
+hbase> list_quotas USER => 'u1, NAMESPACE => 'ns2'
# list quotas that apply to a given user on a namespace
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.util.TestProcessBasedCluster
org.apache.hadoop.hbase.mapreduce.TestImportExport
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/14061//testReport/
Release Findbugs (version 2.0.3) warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/14061//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/14061//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/14061//console
This message is automatically generated.
> Expand information about HBase quotas
> -------------------------------------
>
> Key: HBASE-13699
> URL: https://issues.apache.org/jira/browse/HBASE-13699
> Project: HBase
> Issue Type: Bug
> Components: documentation
> Reporter: Misty Stanley-Jones
> Assignee: Misty Stanley-Jones
> Fix For: 2.0.0
>
> Attachments: HBASE-13699-1.patch, HBASE-13699.patch
>
>
> See HBASE-13398 and
> http://blog.cloudera.com/blog/2014/12/new-in-cdh-5-2-improvements-for-running-multiple-workloads-on-a-single-hbase-cluster/.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
