hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9097) Set HBASE_CLASSPATH before rest of the classpath
Date Wed, 31 Jul 2013 21:37:49 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725746#comment-13725746
] 

Hadoop QA commented on HBASE-9097:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12595100/hbase-9097-v0.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 hadoop1.0{color}.  The patch compiles against the hadoop 1.0 profile.

    {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 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.thrift.TestThriftServer

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//testReport/
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/6547//console

This message is automatically generated.
                
> Set HBASE_CLASSPATH before rest of the classpath
> ------------------------------------------------
>
>                 Key: HBASE-9097
>                 URL: https://issues.apache.org/jira/browse/HBASE-9097
>             Project: HBase
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 0.98.0, 0.95.2, 0.94.11
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>         Attachments: hbase-9097-v0.patch
>
>
> We encountered this when one of the hadoop test jars (specifically hadoop-mapreduce-client-jobclient-2.0.0-cdh4.3.0-tests.jar,
but that's beside the point) had an hdfs-site.xml. This clobbered the hdfs-site.xml that we
included on the classpath via HBASE_CLASSPATH in hbase-env.sh, meaning the master didn't start
in HA NN mode, because the proxy-provider wasn't found in the hdfs-site.xml from the test
jar (even though it was in our config file) because that was the first resolution of that
file.
> This should be a fairly simple fix in bin/hbase, but has some potentially wide-ranging
effects on existing installs that just 'happen' to work.
> Generally, I'd expect things set on the HBASE_CLASSPATH to take precedence over anything
else when starting the hbase daemon.

--
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

Mime
View raw message