Henrik Schröder wrote:
Unfortunately most client libraries perform server selection slightly
differently from each other. It might be possible to get the same
distribution if you use the naive server selection in both, and setup
your list of servers the same way.
On the other hand, does it really matter? Changing your cache client is
kinda a big deal, I wouldn't do that on a running system, what if you
have processes that are in the middle of changing your cached data? No,
your best option is to bring your application down, release the change,
and bring it back up again. You might also want to flush the cache to
make sure you won't get any synchronization errors.
On the other hand, it shouldn't matter. The worst thing that should happen if
one client picks a different server than another is that you use the memory less
efficiently and you'll hit the backend data store a bit more frequently. If you
are counting on everything having a time-synchronized view of exactly the same
data, you probably shouldn't be using a distributed cache.
--
Les Mikesell
[email protected]
