Hi Timur, Java client supports this feature out of the box. Anyway, some users prefer to use a custom DNS/load balancer in front of OrientDB to manually manage fault tolerance together with balancing, see http://orientdb.com/docs/last/Distributed-Configuration.html
2015-08-19 13:33 GMT+02:00 Timur Nasibullin <[email protected]>: > I have multi-node OrientDB configuration with nodes, let say, node1, > node2, etc. > Client is connected to node1, and if node1 goes down because of failure or > maintenance issues, client can't connect to DB. Do anybody have ideas how > to build such system, where client will be transparently switched to > another node in case of failure? > > -- > > --- > 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. > -- --- 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.
