Daniel-Constantin Mierla wrote:
The hash function was tested to get pretty fair distribution for AoR, most of the hashed values respect this format. If 90% of your users end up to same server, then you may need to code a bit :-) and add an alternative hash function to the module. For me the existing one seems good so far.
I do not need to know where a user call is going. Practically, they could share the same db backend for auth, but the location and other user profiles details may be in memory for speed purposes. In what I am doing, all the servers in a group have same config, if i add a new one, I get a new dispersion of the users across servers.
Ah, yes. That makes complete sense. With round-robin I would only get RR distribution at the transactional level, but not based on any characteristics of the request. Thank you for clearing all that up!