Elasticsearch error

Disruptive Solutions

unread,

Nov 20, 2016, 5:32:28 PM11/20/16

to Aurelius

Gremlin-Server (org.apache.tinkerpop.gremlin.server.GremlinServer) does not appear in the java process table
Cassandra (org.apache.cassandra.service.CassandraDaemon) is running with pid 5548
Elasticsearch (org.elasticsearch.bootstrap.Elasticsearch) is running with pid 5917

Oke so Elastic is runnig, but when I start with bin/titan.sh I am getting:

Forking Cassandra...
Running `nodetool statusthrift`.... OK (returned exit status 0 and printed string "running").
Forking Elasticsearch...
Connecting to Elasticsearch (192.168.0.41:9300)............................... timeout exceeded (60 seconds): could not connect to 192.168.0.41:9300
See titan-1.0.0-hadoop1/bin/../log/elasticsearch.log for Elasticsearch log output.

log:
[2016-11-20 17:16:39,054][ERROR][bootstrap ] [DS] Exception
org.elasticsearch.transport.BindTransportException: Failed to bind to [9300]

What am I doing wrong?

Disruptive Solutions

unread,

Nov 23, 2016, 3:29:49 PM11/23/16

to Aurelius

I have been installing Elasticsearch 1.5.1 as stand alone. And have all the services running so it seems. Now I get errors like:
Internal error processing describe_schema_versions

So searching further to get a stable cluster running of: Elastic + Gremlin(titan) + Cassandra and where Cassandra is running on two nodes (cluster) and TitanDB and Gremlin on 1..... it still seems that Gremlin and TitanDB is a Single Point of Failure....

Op zondag 20 november 2016 23:32:28 UTC+1 schreef Disruptive Solutions:

Disruptive Solutions

unread,

Nov 24, 2016, 2:24:19 PM11/24/16

to Aurelius

All working now. Cassandra was not up!

Op woensdag 23 november 2016 21:29:49 UTC+1 schreef Disruptive Solutions:

Reply all

Reply to author

Forward