Re: Riak doesn't use consistent hashing

The "not found" issue is a different one, but related. The issue there is that when a node joins the ring, the ring state is immediately changed. However, it takes time to handoff partitions to new owners. During that time, if a request comes in for data which has > r of its replicas on partitio

Re: Riak doesn't use consistent hashing.

Excellent. Let me know what I can do to help. -Greg On Thursday, May 26, 2011 at 7:37 AM, Justin Sheehy wrote: > Hi, Greg. > > Thanks for your thoughtful analysis and the pull request. > > On Thu, May 26, 2011 at 1:54 AM, Greg Nelson wrote: > > > However, the skipping bit isn't part of > > Ri

Re: Riak doesn't use consistent hashing.

Hi, Greg. Thanks for your thoughtful analysis and the pull request. On Thu, May 26, 2011 at 1:54 AM, Greg Nelson wrote: > However, the skipping bit isn't part of > Riak's preflist calculation.  Instead, nodes claim partitions in such a way > as to be spaced out by target_n_val, to obviate the n

Re: Riak doesn't use consistent hashing

Performance is fine. However requests get a "not found" response for an extended period of time. See http://lists.basho.com/pipermail/riak-users_lists.basho.com/2011-May/thread.html#4078for previous discussion of what sounds like the same issue. On Thu, May 26, 2011 at 6:57 AM, Jonathan Langevin

Re: Riak doesn't use consistent hashing

That sounds quite disconcerting. What happens to the performance of the cluster when this occurs?* Jonathan Langevin Systems Administrator Loom Inc. Wilmington, NC: (910) 241-0433 - jlange...@loomlearning.com - www.loomlearning.com - Skype: intel352 * On Thu, May 2

Riak doesn't use consistent hashing

I've been doing some digging through the details of how a node joins a cluster. When you hear that Riak uses consistent hashing, you'd expect it to distribute keys to nodes by hashing keys onto the ring AND hashing nodes onto the ring. Keys belong to the closest node on the ring, in the clockwis