[
https://issues.apache.org/jira/browse/HBASE-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595988#comment-13595988
]
Hadoop QA commented on HBASE-8025:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572542/HBASE-8025-0.94.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 hadoop2.0{color}. The patch compiles against the hadoop
2.0 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:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4713//console
This message is automatically generated.
> zkcli fails when SERVER_GC_OPTS is enabled
> ------------------------------------------
>
> Key: HBASE-8025
> URL: https://issues.apache.org/jira/browse/HBASE-8025
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.4
> Reporter: Dave Latham
> Fix For: 0.95.0, 0.98.0, 0.94.7
>
> Attachments: HBASE-8025-0.94.patch
>
>
> HBASE-7091 added logic to separate GC logging options for some client
> commands versus server commands. It uses a list of known client commands
> ("shell" "hbck" "hlog" "hfile" "zkcli") and uses the server GC logging
> options for all other invocations of bin/hbase. When zkcli is invoked, it in
> turn invokes "hbase org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg"
> to gather the server command line arguments, but because
> org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServerArg is not on the white
> list it enables server GC logging, which causes extra output that causes the
> zkcli invocation to break. HBASE-7153 addressed this but the fix only solved
> the array syntax - not the white list, so the zkcli command still fails.
> There are many other tools you can invoke that are more likely to "client"
> than "server" options. For example, "bin/hbase org.jruby.Main
> region_mover.rb" or "bin/hbase org.apache.hadoop.hbase.mapreduce.CopyTable"
> or "bin/hbase version" or "bin/hbase
> org.apache.hadoop.hbase.mapreduce.Export". The whitelist of server commands
> is shorter and easier to maintain than a whitelist of client commands.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira