Having exactly the same problem. @dave - did you manage to get it working?
F On Wednesday, 4 June 2014 09:50:54 UTC+1, dave lau wrote: > > Hi, I am relatively new to OrientDB. > I have developed a Glassfish server application that uses OrientDB, now I > want my application to have HA. > I followed the distributed database tutorial > > https://github.com/orientechnologies/orientdb/wiki/Tutorial%3A-setup-a-distributed-database > Everything behaved as said on the tutorial until the part where I am told > to shutdown node 1. > When I shut down node 1, on node 2 instead of showing a message like this > (as written on the tutorial) > > INFO [192.168.1.179]:2435 [orientdb] Removing Member [192.168.1.179]:2434 > [ClusterService] > INFO [192.168.1.179]:2435 [orientdb] > Members [1] { > Member [192.168.1.179]:2435 this > } > [ClusterService] > WARN [node1384015873680] node removed id=Member [192.168.1.179]:2434 > name=node1384014656983 [OHazelcastPlugin] > > I get a message like this. > > 2014-06-04 07:48:52:822 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Connection [Address[10.1.12.18]:2434] lost. Reason: > java.io.EOFException[Remote socket closed!] [TcpIpConnection] > > 2014-06-04 07:48:52:823 WARN [10.1.12.19]:2434 [orientdb_test] [3.2.1] > hz._hzInstance_1_orientdb_test.IO.thread-in-0 Closing socket to endpoint > Address[10.1.12.18]:2434, Cause:java.io.EOFException: Remote socket closed! > [ReadHandler] > > 2014-06-04 07:48:53:355 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Connecting to /10.1.12.18:2434, timeout: 0, bind-any: true [SocketConnector] > > 2014-06-04 07:49:56:487 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] Could > not connect to: /10.1.12.18:2434. Reason: SocketException[Connection timed > out to address /10.1.12.18:2434] [SocketConnector] > > 2014-06-04 07:49:57:373 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Connecting to /10.1.12.18:2434, timeout: 0, bind-any: true [SocketConnector] > > 2014-06-04 07:51:00:487 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] Could > not connect to: /10.1.12.18:2434. Reason: SocketException[Connection timed > out to address /10.1.12.18:2434] [SocketConnector] > > 2014-06-04 07:51:01:387 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Connecting to /10.1.12.18:2434, timeout: 0, bind-any: true [SocketConnector] > > 2014-06-04 07:52:04:551 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] Could > not connect to: /10.1.12.18:2434. Reason: SocketException[Connection timed > out to address /10.1.12.18:2434] [SocketConnector] > > 2014-06-04 07:52:04:552 WARN [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Removing connection to endpoint Address[10.1.12.18]:2434 Cause => > java.net.SocketException {Connection timed out to address /10.1.12.18:2434}, > Error-Count: 5 [ConnectionMonitor] > > 014-06-04 07:52:04:554 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] Master > Address[10.1.12.18]:2434 left the cluster. Assigning new master Member > [10.1.12.19]:2434 this [ClusterService] > > 2014-06-04 07:52:04:554 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > Removing Member [10.1.12.18]:2434 [ClusterService] > > 2014-06-04 07:52:04:581 WARN [test2] node removed id=Member [10.1.12.18]:2434 > name=test1 [OHazelcastPlugin] > > 2014-06-04 07:52:04:582 INFO [test2] removing queue > 'orientdb.node.test1.response' containing 0 messages > [OHazelcastDistributedMessageService] > > 2014-06-04 07:52:04:584 INFO [10.1.12.19]:2434 [orientdb_test] [3.2.1] > > From there, I can't connect to node 2 from console that has connection to > node 1 (which the tutorial said the console would automatically switch over > the connection) > > Also, once I started node 1 again, the two databases would no longer sync. > > Thank you in advance! > > > > -- --- 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 orient-database+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
