Hi,
I'm trying to connect from windows system(dev envirnoment) to linux server(hbase is installed). I'm facing this issue
ERROR [localhost-startStop-1] schemamanager.HBaseSchemaManager (HBaseSchemaManager.java:update(112)) - Either check for network connection or table isn't in enabled state, Caused by:
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:
We are on windows 10 system
Even i have added entry in etc/hosts
172.16.0.157 UCSL-GKL-HDP-07
Windows fire wall is turned off
Antivirus is turned off
Windows defender is turned off
We are getting this error after this step
"Session establishment complete on server"
Actual log is as below
2017-09-15 19:50:03,934 WARN [localhost-startStop-1] util.NativeCodeLoader (NativeCodeLoader.java:(62)) - Unable to load native-hadoop library for your platform... using builtin-java classes where applicable
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:zookeeper.version=3.4.5-1392090, built on 09/30/2012 17:52 GMT
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:host.name=U.com
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.version=1.8.0_131
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.vendor=Oracle Corporation
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.home=C:\Program Files\Java\jdk1.8.0_131\jre
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.class.path=E:\jeevi\NewEclipse\apache-tomcat-7\bin\bootstrap.jar;E:\jeevi\NewEclipse\apache-tomcat-7\bin\tomcat-juli.jar;C:\Program Files\Java\jdk1.8.0_131\lib\tools.jar
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.library.path=C:\Program Files\Java\jdk1.8.0_131\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:/Program Files/Java/jre1.8.0_131/bin/server;C:/Program Files/Java/jre1.8.0_131/bin;C:/Program Files/Java/jre1.8.0_131/lib/amd64;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Skype\Phone;C:\Program Files\Java\jdk1.8.0_131\bin;C:\apache-maven-3.1.1\bin;C:\Users\jeevitesh\AppData\Local\Microsoft\WindowsApps;;C:\Users\jeevitesh\AppData\Local\Programs\Fiddler;E:\jeevi\NewEclipse\eclipse;;.
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.io.tmpdir=C:\Users\JEEVIT~1\AppData\Local\Temp
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:java.compiler=<NA>
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:os.name=Windows 10
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:os.arch=amd64
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:os.version=10.0
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:user.name=Jeevitesh
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:user.home=C:\Users\jeevitesh
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (Environment.java:logEnv(100)) - Client environment:user.dir=E:\jeevi\NewEclipse\eclipse
2017-09-15 19:50:04,203 INFO [localhost-startStop-1] zookeeper.ZooKeeper (ZooKeeper.java:(438)) - Initiating client connection, connectString=172.16.0.157:2181 sessionTimeout=90000 watcher=hconnection-0x573d820e, quorum=172.16.0.157:2181, baseZNode=/hbase
2017-09-15 19:50:04,466 INFO [localhost-startStop-1] zookeeper.RecoverableZooKeeper (RecoverableZooKeeper.java:(120)) - Process identifier=hconnection-0x573d820e connecting to ZooKeeper ensemble=172.16.0.157:2181
2017-09-15 19:50:04,466 INFO [localhost-startStop-1-SendThread(UCSL-GKL-HDP-07:2181)] zookeeper.ClientCnxn (ClientCnxn.java:logStartConnect(966)) - Opening socket connection to server UCSL-GKL-HDP-07/172.16.0.157:2181. Will not attempt to authenticate using SASL (unknown error)
2017-09-15 19:50:04,489 INFO [localhost-startStop-1-SendThread(UCSL-GKL-HDP-07:2181)] zookeeper.ClientCnxn (ClientCnxn.java:primeConnection(849)) - Socket connection established to UCSL-GKL-HDP-07/172.16.0.157:2181, initiating session
2017-09-15 19:50:04,489 INFO [localhost-startStop-1-SendThread(UCSL-GKL-HDP-07:2181)] zookeeper.ClientCnxn (ClientCnxn.java:onConnected(1207)) - Session establishment complete on server UCSL-GKL-HDP-07/172.16.0.157:2181, sessionid = 0x15e8594c511000a, negotiated timeout = 40000
2017-09-15 19:59:48,921 ERROR [localhost-startStop-1] schemamanager.HBaseSchemaManager (HBaseSchemaManager.java:update(112)) - Either check for network connection or table isn't in enabled state, Caused by:
org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after attempts=35, exceptions:
Fri Sep 15 19:50:06 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, java.net.ConnectException: Connection refused: no further information
Fri Sep 15 19:50:06 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, org.apache.hadoop.hbase.ipc.RpcClient$FailedServerException: This server is in the failed servers list: UCSL-GKL-HDP-07/172.16.0.157:32398
Fri Sep 15 19:50:07 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, org.apache.hadoop.hbase.ipc.RpcClient$FailedServerException: This server is in the failed servers list: UCSL-GKL-HDP-07/172.16.0.157:32398
Fri Sep 15 19:50:08 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, org.apache.hadoop.hbase.ipc.RpcClient$FailedServerException: This server is in the failed servers list: UCSL-GKL-HDP-07/172.16.0.157:32398
Fri Sep 15 19:50:11 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, java.net.ConnectException: Connection refused: no further information
Fri Sep 15 19:50:16 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e23, java.net.ConnectException: Connection refused: no further information
Fri Sep 15 19:50:27 IST 2017, org.apache.hadoop.hbase.client.RpcRetryingCaller@678b6e
Below is persistance file
com.impetus.kundera.KunderaPersistence
As you can see "update" in "kundera.ddl.auto.prepare" . I'm expecting all the tables to be created.
Any suggestion towards this issue will help me a lot.
Hi @jeevitesh,
Use kundera-hbase-v2 module instead of kundera-hbase. Use this dependency:
<dependency>
<groupId>com.impetus.kundera.client</groupId>
<artifactId>kundera-hbase-v2</artifactId>
<version>${kundera.version}</version>
</dependency>
Check Kundera with HBase for more details.
-Dev
I have done those changes still error persists. I have sent(by mail : gmail) a sample project where you can reproduce the issue. kindly help us in this regard.
Hi @jeevitesh,
Lets discuss this over gitter chat.
-Dev
Hi @jeevitesh,
First of all, use only latest version of Kundera and kundera-hbase-v2 module.
We tested it with 1.2, 1.0 & 0.96 HBase versions.
kundera-elastic-search is needed if you want to store indexes in elasticsearch along with data in HBase. I recommend start with only kundera-hbase-v2. Once you are able to perform simple queries then you can use kundera-elastic-search for aggregation queries.
It looks like a connection problem. Start without using schema generation feature and create schema at your own.
-Dev
Hi Devendar,
Thanks for the response.. Currently there are no store indexes..
"Start without using schema generation feature" not able to understand this
can kindly explain
thnaks
jeevitesh
On Thu, Oct 5, 2017 at 12:33 PM, Devender Yadav [email protected]
wrote:
Hi @jeevitesh https://github.com/jeevitesh,
First of all, use only latest version of Kundera and kundera-hbase-v2
module.
We tested it with 1.2, 1.0 & 0.96 HBase versions.
kundera-elastic-search is needed if you want to store indexes in
elasticsearch along with data in HBase. I recommend start with only
kundera-hbase-v2. Once you are able to perform simple queries then you
can use kundera-elastic-search for aggregation queries.
It looks like a connection problem. Start without using schema generation
feature.
-Dev
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/impetus-opensource/Kundera/issues/968#issuecomment-334377043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGagwwCbmIqr_ikuaauUF2YeAQJuKFw5ks5spH8tgaJpZM4PZISg
.
Hi @jeevitesh,
You added schema auto-generation property in persistence.xml
<property name="kundera.ddl.auto.prepare" value="update" />
This is creating HTable for your entity in HBase. Since you are getting the issue in HBaseSchemaManager, so I recommended to create HTable yourself and remove that property from the persistence.xml.
-Dev