Hey all, I noticed that in the docs, there is mention of Load Balancing prior to v2.2 (currently in alpha) via DNS record:
Before v2.2, the simplest and most powerful way to achieve load balancing > seems to use some hidden (to some) properties of DNS. The trick is to > create a TXT record listing the servers. > > The format is: > > v=opf<version> (s=<hostname[:<port>]> )* > > Example of TXT record for domain *dbservers.mydomain.com*: > > v=opf1 s=192.168.0.101:2424 s=192.168.0.133:2424 > > In this way if you open a database against the URL > remote:dbservers.mydomain.com/demo the OrientDB client library will try > to connect to the address *192.168.0.101* port 2424. If the connection > fails, then the next address *192.168.0.133:* port 2424 is tried. > > To enable this feature in Java Client driver set > network.binary.loadBalancing.enabled=true: > > java ... -Dnetwork.binary.loadBalancing.enabled=true > > or via Java code: > > OGlobalConfiguration.NETWORK_BINARY_DNS_LOADBALANCING_ENABLED.setValue(true); > > This seems rather interesting -- but the description seems to imply that it's *failover* rather than *load balancing*. Can I get some clarifications here? If a client connects to a list of servers following the above method, does it vary which servers it connects to, or does it always proceed in linear order (tries the first one, if that fails, tries the next, etc.) ? If it proceeds in linear order, this would mean that server 1 would always get all the load, until its locked up or dead, at which point requests would spill over to server 2, so its not truly balancing. Would be great to get some clarifications! -- --- 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.
