You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2012/12/04 04:53:58 UTC
[jira] [Created] (HBASE-7269) Testing in place does not work if not
building with default profile
Andrew Purtell created HBASE-7269:
-------------------------------------
Summary: Testing in place does not work if not building with default profile
Key: HBASE-7269
URL: https://issues.apache.org/jira/browse/HBASE-7269
Project: HBase
Issue Type: Bug
Affects Versions: 0.96.0
Reporter: Andrew Purtell
If I build with the Hadoop 2 profile, for example:
{{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
and then try to run daemons like so:
{{./bin/hbase master start}}
this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
{noformat}
12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
at $Proxy10.regionServerStartup(Unknown Source)
at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
... 4 more
Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
{noformat}
There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509917#comment-13509917 ]
Jean-Daniel Cryans commented on HBASE-7269:
-------------------------------------------
Wouldn't running clean first just be cleaner? Another similar problem I got is if switching profile without cleaning and then using the created tarball, it will contain both hadoop 1 and 2 jars.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510793#comment-13510793 ]
Enis Soztutar commented on HBASE-7269:
--------------------------------------
N, do you know what this was in bin/hbase in the first place? Does not make sense to me.
{code} we need hbase-it to always be the last module run. since it has the largest classpath
{code}
Thinking about it, the patch makes sense. We should not be doing mvn invocation from bin/hbase.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
> Attachments: 7269.v1.patch
>
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510041#comment-13510041 ]
Enis Soztutar commented on HBASE-7269:
--------------------------------------
@JD running clean + compile + classpath would be too long to be executed from the bin/hbase script I am afraid. If we had save classpath, you can do clean compile before switching to h2.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510043#comment-13510043 ]
Jean-Daniel Cryans commented on HBASE-7269:
-------------------------------------------
[~enis], I meant to say that clean should run by the dev before switching profile.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510199#comment-13510199 ]
Andrew Purtell commented on HBASE-7269:
---------------------------------------
I did a 'mvn clean install' of the Hadoop 2 profile then tried to invoke bin/hbase. It changed the cached classpath and used the Hadoop 1 profile because bin/hbase doesn't know and had no way to specify what profile was used for building.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509512#comment-13509512 ]
stack commented on HBASE-7269:
------------------------------
Or at least, not replace it if already exists (if none, it should generate one else every startup will take a long time).
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509538#comment-13509538 ]
Andrew Purtell commented on HBASE-7269:
---------------------------------------
bq. We can just add a save cache classpath execution to compile, and that should work.
Very reasonable.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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] [Updated] (HBASE-7269) Testing in place does not work if not
building with default profile
Posted by "nkeywal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nkeywal updated HBASE-7269:
---------------------------
Attachment: 7269.v1.patch
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
> Attachments: 7269.v1.patch
>
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510797#comment-13510797 ]
stack commented on HBASE-7269:
------------------------------
[~eclark] did the above hbase-it trickery... hey Elliott!
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
> Attachments: 7269.v1.patch
>
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509510#comment-13509510 ]
Enis Soztutar commented on HBASE-7269:
--------------------------------------
Maybe bin/hbase should not even invoke mvn, but just refer to cached classpath. We can save the classpath in mvn compile.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "nkeywal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509577#comment-13509577 ]
nkeywal commented on HBASE-7269:
--------------------------------
I've added the possibility to have options to the mvn command in HBASE-7168. But Enis suggestion seems good.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "nkeywal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510483#comment-13510483 ]
nkeywal commented on HBASE-7269:
--------------------------------
What do you think of the patch? It's the implementation of Enis' proposal. Locally it seems to work (but it's just a brief test, and, well, you know, maven...)
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
> Attachments: 7269.v1.patch
>
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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-7269) Testing in place does not work if
not building with default profile
Posted by "Enis Soztutar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13509518#comment-13509518 ]
Enis Soztutar commented on HBASE-7269:
--------------------------------------
It already checks for the file existence. We can just add a save cache classpath execution to compile, and that should work.
> Testing in place does not work if not building with default profile
> -------------------------------------------------------------------
>
> Key: HBASE-7269
> URL: https://issues.apache.org/jira/browse/HBASE-7269
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.96.0
> Reporter: Andrew Purtell
>
> If I build with the Hadoop 2 profile, for example:
> {{mvn -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-SNAPSHOT}}
> and then try to run daemons like so:
> {{./bin/hbase master start}}
> this will fail, because the launch script will invoke Maven to build the cached classpath selecting whatever is the default profile, currently Hadoop 1. Startup will actually get pretty far, until:
> {noformat}
> 12/12/04 11:42:13 WARN regionserver.HRegionServer: error telling master we are up
> com.google.protobuf.ServiceException: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:189)
> at $Proxy10.regionServerStartup(Unknown Source)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.reportForDuty(HRegionServer.java:1844)
> at org.apache.hadoop.hbase.regionserver.HRegionServer.run(HRegionServer.java:843)
> at java.lang.Thread.run(Thread.java:679)
> Caused by: java.lang.NoClassDefFoundError: org/apache/hadoop/net/SocketInputWrapper
> at org.apache.hadoop.hbase.ipc.HBaseClient.createConnection(HBaseClient.java:317)
> at org.apache.hadoop.hbase.ipc.HBaseClient.getConnection(HBaseClient.java:1415)
> at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:1278)
> at org.apache.hadoop.hbase.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:177)
> ... 4 more
> Caused by: java.lang.ClassNotFoundException: org.apache.hadoop.net.SocketInputWrapper
> {noformat}
> There doesn't appear to be a way to supply additional arguments to the launch script for directing Maven which profile(s) to activate.
--
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