InstanceNotFoundException: LilyHBaseProxy:name=ReplicationPeer

[jean...@spaggiari.org]

Hi,

I now try to run the test against a real HBase cluster but I face the error below. Cluster is Hadoop 2.4.1 + HBase 0.98.5.

Can the issue below be because of the versions I use?

Ran mvn -Pconnect -DargLine="-Dlily.test.hbase.zookeeper.quorum=hbm101 -Dlily.test.hbase.zookeeper.property.clientPort=2181 -Dlily.test.dfs=hdfs://hbm101:8020" test

Both HBase cluster and Hadoop are currently running well.

Any idea?

Thanks,

JM

cat ~/lilyproject/cr/repository/test/target/log.txt

[main] WARN  org.apache.hadoop.util.NativeCodeLoader - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
[main] INFO  org.apache.zookeeper.ZooKeeper - Initiating client connection, connectString=hbm101:2181 sessionTimeout=180000 watcher=hconnection
[main-SendThread(hbm101:2181)] INFO  org.apache.zookeeper.ClientCnxn - Opening socket connection to server hbm101/10.0.1.201:2181. Will not attempt to authenticate using SASL (unknown error)
[main] INFO  org.apache.hadoop.hbase.zookeeper.RecoverableZooKeeper - The identifier of this process is 25059@hde101
[main-SendThread(hbm101:2181)] INFO  org.apache.zookeeper.ClientCnxn - Socket connection established to hbm101/10.0.1.201:2181, initiating session
[main-SendThread(hbm101:2181)] INFO  org.apache.zookeeper.ClientCnxn - Session establishment complete on server hbm101/10.0.1.201:2181, sessionid = 0x148020e68010160, negotiated timeout = 40000
[main] INFO  org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation - Closed zookeeper sessionid=0x148020e68010160
[main] INFO  org.apache.zookeeper.ZooKeeper - Session: 0x148020e68010160 closed
[main-EventThread] INFO  org.apache.zookeeper.ClientCnxn - EventThread shut down
[main] ERROR org.lilyproject.util.io.Closer - Error closing object of type org.lilyproject.hadooptestfw.HBaseProxy
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.lilyproject.util.io.Closer.close(Closer.java:61)
        at org.lilyproject.repotestfw.RepositorySetup.stop(RepositorySetup.java:278)
        at org.lilyproject.repository.impl.test.TypeManagerRecordTypeTest.tearDownAfterClass(TypeManagerRecordTypeTest.java:45)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
        at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
        at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
        at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
        at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
        at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
        at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
        at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
        at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
        at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:172)
        at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:78)
        at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:70)
Caused by: javax.management.InstanceNotFoundException: LilyHBaseProxy:name=ReplicationPeer
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1095)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.exclusiveUnregisterMBean(DefaultMBeanServerInterceptor.java:427)
        at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.unregisterMBean(DefaultMBeanServerInterceptor.java:415)
        at com.sun.jmx.mbeanserver.JmxMBeanServer.unregisterMBean(JmxMBeanServer.java:546)
        at org.lilyproject.hadooptestfw.HBaseProxy.stop(HBaseProxy.java:329)
        ... 28 more

[Karel Vervaeke]

For a first run I would recommend running against the versions that come with CDH4.4.0.

I would not be surprised if there turns out to be an effort involved in making things work with significantly different versions.

Btw: There is a public maven repository; For projects using Lily you may prefer to use that rather than building yourself.

http://lilyproject.org/maven/maven2/deploy/

HTH,

Karel

--
You received this message because you are subscribed to the Google Groups "lily-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lily-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jean-Marc Spaggiari]

I have suspected the versions to be an issue, so I have also built a 0.94.23+hadoop 1.2.1 cluster but tests fail also on this one.  I'm looking at it now.

Do you know if there is a specific JDK version supported by Lily? Or boty 1.6 and 1.7 are fine?

Thanks,

JM

[Jean-Marc Spaggiari]

Ok. On the 0.94 cluster I was missing Hadoop native lib in the LD_LIBRARY_PATH. fixing this now gives me the exact same error as 0.98.5.

Continuing investigations...

[Karel Vervaeke]

Another idea is to first try without -Pconnect, to rule out other setup problems.

For those to work you should make sure you don't have your hostname linked to 127.0.1.1 in your /etc/hosts. That's usually the first problem people encounter. Your hostname should be on 127.0.0.1.

Regards,

Karel