JanusGraph seems to force embedded ElasticSearch


Jason Plurad <plu...@...>
 

This commonly happens if you're connecting to a graph instance that was previously created. The initial configuration is stored within the graph itself.

For BerkeleyJE, try pointing storage.directory to a new location or deleting the existing db/berkeley directory.
For Cassandra, try using a different storage.cassandra.keyspace or dropping the existing keyspace.
For HBase, try using a different storage.hbase.table or dropping the existing table.

-- Jason


On Friday, August 25, 2017 at 12:28:27 PM UTC-4, Mike Thomsen wrote:
This is my configuration:

gremlin.graph=org.janusgraph.core.JanusGraphFactory
storage.backend=berkeleyje
storage.directory=db/berkeley
index.search.backend=elasticsearch
index.search.hostname=127.0.0.1
index.search.elasticsearch.client-only=true

i loaded it with Gremlin like this:

graph = JanusGraphFactory.open('conf/janusgraph-berkeleyje-es.properties')

But it insists on creating an embedded ElasticSearch node at db/es despite a remote connection being specified.

What am I doing wrong?

Thanks,

Mike


mikert...@...
 

This is my configuration:

gremlin.graph=org.janusgraph.core.JanusGraphFactory
storage.backend=berkeleyje
storage.directory=db/berkeley
index.search.backend=elasticsearch
index.search.hostname=127.0.0.1
index.search.elasticsearch.client-only=true

i loaded it with Gremlin like this:

graph = JanusGraphFactory.open('conf/janusgraph-berkeleyje-es.properties')

But it insists on creating an embedded ElasticSearch node at db/es despite a remote connection being specified.

What am I doing wrong?

Thanks,

Mike