JanusGraph•5mo ago

RpcRetryingCallerImp while trying to connect JanusGraph with Hbase 2.2.7 under Cloudera Distribution

Hi, I am new to using JanusGraph and I am trying to integrate JanusGraph version 0.6.4 with Kerberized HBase 2.2.7, which comes under the Cloudera Distribution 7.9.1. I had to use an earlier version of JanusGraph since the compatibility matrix specifies that JanusGraph is tested compatible with HBase 2.2.x. I am using the following configuration to get a 3-node HBase cluster to interact with JanusGraph. However, when I try to start the server, I encounter the following loop, and as a result, the server does not start. I installed JanusGraph on one of the cluster nodes, specifically at 192.168.0.1, and I am trying to run it there. I am not sure how to go about solving this, and I presume ZooKeeper is connected but HBase can’t due to Kerberos authentication.  

8153 [main] INFO  org.apache.hadoop.hbase.client.RpcRetryingCallerImpl  - Call exception, tries=6, retries=16, started=4743 ms ago, cancelled=false, msg=Call to 192.168.0.1:16020 failed on local exception: org.apache.hadoop.hbase.exceptions.ConnectionClosedException: Connection closed, details=row 'ConfigurationManagementGraph' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=192.168.0.1,16020,1715799777729, seqNum=-1, see https://s.apache.org/timeout

8153 [main] INFO  org.apache.hadoop.hbase.client.RpcRetryingCallerImpl  - Call exception, tries=6, retries=16, started=4743 ms ago, cancelled=false, msg=Call to 192.168.0.1:16020 failed on local exception: org.apache.hadoop.hbase.exceptions.ConnectionClosedException: Connection closed, details=row 'ConfigurationManagementGraph' on table 'hbase:meta' at region=hbase:meta,,1.1588230740, hostname=192.168.0.1,16020,1715799777729, seqNum=-1, see https://s.apache.org/timeout

Core configs of gremlin-server.yaml:  

host: 192.168.0.1
port: 8182
evaluationTimeout: 30000
channelizer: org.apache.tinkerpop.gremlin.server.channel.WsAndHttpChannelizer
graphManager: org.janusgraph.graphdb.management.JanusGraphManager
graphs: {
  ConfigurationManagementGraph: conf/janusgraph-hbase-config.properties
}

host: 192.168.0.1
port: 8182
evaluationTimeout: 30000
channelizer: org.apache.tinkerpop.gremlin.server.channel.WsAndHttpChannelizer
graphManager: org.janusgraph.graphdb.management.JanusGraphManager
graphs: {
  ConfigurationManagementGraph: conf/janusgraph-hbase-config.properties
}

In conf/janusgraph-hbase-config.properties:

gremlin.graph=org.janusgraph.core.ConfiguredGraphFactory
graph.graphname=ConfigurationManagementGraph
storage.backend=hbase
storage.hostname=192.168.0.1,192.168.0.2,192.168.0.3
cache.db-cache = true
cache.db-cache-clean-wait = 20
cache.db-cache-time = 180000
cache.db-cache-size = 0.5

gremlin.graph=org.janusgraph.core.ConfiguredGraphFactory
graph.graphname=ConfigurationManagementGraph
storage.backend=hbase
storage.hostname=192.168.0.1,192.168.0.2,192.168.0.3
cache.db-cache = true
cache.db-cache-clean-wait = 20
cache.db-cache-time = 180000
cache.db-cache-size = 0.5

1 Reply

paull8147•4mo ago

Hello, from memory, I manage to have hbase kerberised with this zookeeper conf hbase.zookeeper.quorum=192.168.100.1,... zookeeper.znode.parent=/hbase-secure hbase.zookeeper.property.clientPort=2181 at a moment, i needed to open hbase port 16020 I don't know if it can help

Gaming

Programming

RpcRetryingCallerImp while trying to connect JanusGraph with Hbase 2.2.7 under Cloudera Distribution