Causal Clustering nodes refuse to discover each other

217 views
Skip to first unread message

Kyle

unread,
Sep 2, 2017, 9:37:13 PM9/2/17
to Neo4j
Hello,

I am trying to set up a Causal Cluster of 3 Core nodes and 0 read-only nodes. However, all 3 machines get stuck when trying to connect to the other cluster members. I am running the linux CentOS machines in AWS EC2 inside a security group that allows all TCP traffic within the group. I've confirmed that the machines can talk to each other using netcat and curl. I've confirmed using tcpdump that each machine is receiving TCP traffic from the other machines on port 5000, but not on ports 6000 or 7000. I've also tried switching the 3 listen addresses to the commented out lines in the gist below.

$ java -version
java version "1.8.0_77"
Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Java HotSpot(TM) 64-Bit Server VM (build 25.77-b03, mixed mode)

Neo4j Enterprise 3.2.3



netstat -tuplen (machine with <ip1>)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       User       Inode      PID/Program name
tcp        0      0 ::ffff:<ip1>:5000           :::*                        LISTEN      0          387007     -
tcp        0      0 :::6000                     :::*                        LISTEN      0          387061     -
tcp        0      0 :::7000                     :::*                        LISTEN      0          386999     -

Thanks,

Kyle

Kyle

unread,
Sep 5, 2017, 1:14:14 PM9/5/17
to Neo4j
I've also tried Neo4j Enterprise 3.2.2 as well to see if it was a regression. I encountered the same results.

Mark Needham

unread,
Sep 5, 2017, 3:28:09 PM9/5/17
to ne...@googlegroups.com
What do you have the advertised address set as? I've been setting that to the private DNS name of the machines and it seems to work with that setting.

--
You received this message because you are subscribed to the Google Groups "Neo4j" group.
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kyle

unread,
Sep 6, 2017, 11:39:19 AM9/6/17
to Neo4j
I set the advertised address to the private IP of the instances. I've now also tried the hostname as well without any luck. We don't expose the boxes to the open internet and instead use a VPN to connect so there are no public IPs. Is there a verbose flag or some other log file that I can use to better debug the issue?
To unsubscribe from this group and stop receiving emails from it, send an email to neo4j+un...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages