Supposedly, -Dnetwork.binary.loadBalancing.enabled=true enables load balancing, but I think it really just enables automatic fail over.
We use an external DNS service that provides round-robin load balancing for our access, even though it's a completely local service. Real load balancing built into the OrientDB service would be nice, but this solution works for now. -Colin On Tuesday, December 9, 2014 8:45:57 AM UTC-6, Stéphane Schild wrote: > > Version: orientdb-community-2.0-M3 > ---------------------------------------------------- > Hello, > > We want to deploy a scalable OrientDB cluster and have read the following > documents: > 1) > http://www.orientechnologies.com/docs/last/orientdb.wiki/Distributed-Configuration.html > 2) > http://www.orientechnologies.com/docs/last/orientdb.wiki/Distributed-Sharding.html > > According to 1) we should use some DNS trick to enable load-balancing, but > for me it is only a mean to manage fail-over capability. > And according to 2), we can use sharding to partition the data amoung > different nodes/servers (which is how to load-balance the data among > different nodes). > > But how could we have load-balancing on connections to nodes/servers, > meaning that we don't want all our clients to connect to the same > node/server. We would like to have a round-robin strategy for example to > distribute read/write calls amoung all the nodes/servers in the cluster. > > Thank you for your response ! > > Regards > -- --- 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.
