I have also attached the regular and distributed config files I'm using (pretty much the originals) - I just tried using TCP-IP instead of AWS for hazelcast, and the result is the same- it connects to the nodes but they don't find each other.
On Wednesday, June 17, 2015 at 6:43:53 PM UTC-5, Boris Wexler wrote: > > I am trying to setup two orientdb servers on EC2 instances in cluster > configuration, and am 95% of the way there except that the nodes don't seem > to see each other. I've read every post I could find on the topic, but > can't seem to find the issue. > I've attached my hazelcast.xml, as well as the server output at startup > for both. The IP for the first server I'm starting is 172.31.38.104 and for > the second one is 172-31-42-204 - as you will see the second one actually > sees and connects successfully to the first, yet the node doesn't seem to > join the cluster. > > I'm using the orient db 2.06 AMI. > > Thanks in advance for the help > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
default-distributed-db-config.json
Description: Binary data
orientdb-server-config.xml
Description: XML document
