CODEWITHSUNDEEP
neo4j
suryan
suryan

Reputation: 226

neo4j causal clustering, can't form with ec2 instances

Did anyone successfully setup a Neo4j causal cluster?

I'm unable to setup one with 3 ec2 t2.micro instances... all Neo4j servers running but not yet formed cluster (waited for ever).

Is there is any minimum requirement (RAM, etc) ?

This is the log im seeing in 1 of Neo4j server :

2017-07-18 03:35:51.303+0000 INFO  Attempting to connect to the other cluster members before continuing...

also getting below continuously 2017-07-20 17:55:01.963+0000 INFO [o.n.c.c.c.RaftMachine] Election started with vote request: Vote.Request from MemberId{3da30036} {term=250, candidate=MemberId{3da30036}, lastAppended=0, lastLogTerm=0} and members: [MemberId{9e1be61d}, MemberId{3da30036}] 2017-07-20 17:55:10.475+0000 INFO [o.n.c.c.c.m.MembershipWaiter] Leader commit unknown 2017-07-20 17:55:12.919+0000 INFO [o.n.c.c.c.RaftMachine] Election timeout triggered ... not sure why leader unable to elect.

Upvotes: 2

Views: 1529

Answers (1)

suryan
suryan

Reputation: 226

finally able to fix the issue and now my causal clustering is working fine. Basically each neo4j server neo4j.conf should use below property with proper IP number dbms.connectors.default_advertised_address=10.0.0.1 if creating under AWS with ec2 instances this should be private IP of instance and its started working, initially I used public IP of instance

Upvotes: 1

Related Questions