I'm wondering why a TokenRange returned by describe_ring(keyspace) of the
thrift API just returns endpoints consisting only of an address but omits any
port information?
My first thought was, this method could be used to expose some information
about the ring structure to the client, i.e. to
On 08.08.2010, at 14:47 aaron morton wrote:
What sort of client side load balancing where you thinking of? I just use
round robin DNS to distribute clients around the cluster, and have them
recycle their connections every so often.
I was thinking about to use this method to give the
Also, note that lack of saw-toothing is not a goal in and of itself
and may even be bad. For example, with respect to the young generation
the situation is essentially:
(1) The larger the young generation, the more significant the saw-tooth.
(2) The larger the young generation, the more