[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560565#comment-13560565
]
nkeywal commented on HBASE-7637:
You're right, it's not much of an issue.
The patch works with 2.0 and 1.0. Don't forget the clean between the two as I
initially did :-)
+1 so.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560669#comment-13560669
]
nkeywal commented on HBASE-7637:
It's possible to do this (cf. nomodules.patch) in the main pom.xml (on top of
what you did). It has one advantage: you don't download (or need) the hadoop
version you don'tuse. Without it, even if you build hbase for hadoop 1, you
take hadoop 2 as well.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch, nomodules.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560715#comment-13560715
]
Hadoop QA commented on HBASE-7637:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566119/nomodules.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:red}-1 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.master.TestZKBasedOpenCloseRegion
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4146//console
This message is automatically generated.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch, nomodules.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561251#comment-13561251
]
Hudson commented on HBASE-7637:
---
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #369 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/369/])
HBASE-7637 hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
(Revision 1437803)
Result = FAILURE
eclark :
Files :
* /hbase/trunk/bin/hbase
* /hbase/trunk/hbase-it/pom.xml
* /hbase/trunk/pom.xml
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch, nomodules.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13561295#comment-13561295
]
Hudson commented on HBASE-7637:
---
Integrated in HBase-TRUNK #3786 (See
[https://builds.apache.org/job/HBase-TRUNK/3786/])
HBASE-7637 hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
(Revision 1437803)
Result = FAILURE
eclark :
Files :
* /hbase/trunk/bin/hbase
* /hbase/trunk/hbase-it/pom.xml
* /hbase/trunk/pom.xml
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch, nomodules.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559768#comment-13559768
]
nkeywal commented on HBASE-7637:
I don't understand this:
-phasecompile/phase
+phasetest/phase
Does it mean we would need to do mvn test -DskipTests before being able to do
bin/startHbase.sh?
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559806#comment-13559806
]
Elliott Clark commented on HBASE-7637:
--
package, install, or test would work as they all imply test.
Right now, regardless of this patch, compile is broken because of intermodule
dependencies so we're no really losing anything. Everything that could
compile the project implies test.
I moved the phase to test in order to duplicate what
add_maven_test_classes_to_classpath used to give us.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Assignee: Elliott Clark
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13558996#comment-13558996
]
nkeywal commented on HBASE-7637:
I will need to fix it, as it's blocks some MTTR tests. May be I'm actually the
cause of it , with stuff on the pom and cached path. But if someone already
knows exactly what to do, I'm interested :-).
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559020#comment-13559020
]
Ted Yu commented on HBASE-7637:
---
I think this should be related to line 906 in pom.xml:
compat.modulehbase-hadoop1-compat/compat.module
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559024#comment-13559024
]
nkeywal commented on HBASE-7637:
Yes, I tried to change it (and I guess it must be done), but compat1 is still
built and is found in the path.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559034#comment-13559034
]
nkeywal commented on HBASE-7637:
it's not in cached_classpath.txt
But if you do bin/hbase classpath, it shows up.
investigating...
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559037#comment-13559037
]
nkeywal commented on HBASE-7637:
Here is the guilty, in bin/hbase
add_maven_main_classes_to_classpath() {
# assumes all modules are named hbase-* in the top level directory
IFS=$ORIG_IFS
for module in `ls $HBASE_HOME | grep 'hbase-*'`
do
add_to_cp_if_exists $HBASE_HOME/$module/target/classes
done
}
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559040#comment-13559040
]
nkeywal commented on HBASE-7637:
The best option would be to build only the compat module we need. I don't know
if it's possible with maven, but I will try (tomorrow :-)/
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559078#comment-13559078
]
Elliott Clark commented on HBASE-7637:
--
Do we even need that add_maven_main_classes_to_classpath any more ? Seems like
cached_classpath contained all of the jars that I would expect.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
[jira] [Commented] (HBASE-7637) hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
[
https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559163#comment-13559163
]
Hadoop QA commented on HBASE-7637:
--
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12565849/HBASE-7637-0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified tests.
{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:red}-1 findbugs{color}. The patch appears to introduce 3 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 core tests{color}. The patch failed these unit tests:
org.apache.hadoop.hbase.TestLocalHBaseCluster
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/4117//console
This message is automatically generated.
hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0
Key: HBASE-7637
URL: https://issues.apache.org/jira/browse/HBASE-7637
Project: HBase
Issue Type: Bug
Components: build
Affects Versions: 0.96.0
Reporter: nkeywal
Priority: Critical
Fix For: 0.96.0
Attachments: HBASE-7637-0.patch
I'm unclear on the root cause / fix. Here is the scenario:
{noformat}
mvn clean package install -Dhadoop.profile=2.0 -DskipTests
bin/start-hbase.sh
{noformat}
fails with
{noformat}
Caused by: java.lang.ClassNotFoundException:
org.apache.hadoop.metrics2.lib.MetricMutable
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
{noformat}
doing
{noformat}
rm -rf hbase-hadoop1-compat/target/
{noformat}
makes it work.
In the pom.xml, we never reference hadoop2-compat. But doing so does not
help: hadoop1-compat is compiled and takes precedence over hadoop2...
--
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
