You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cassandra.apache.org by Jonathan Ellis <jb...@gmail.com> on 2009/08/01 16:41:29 UTC

Re: about RackAwareStrategy

It's quite possible there's a bug here -- I know we haven't started
using RackAware yet at Rackspace.  I think Digg has looked at it some
but I don't know if they have actually deployed it.  (I was hoping
they'd chime in here... :)

-Jonathan

On Fri, Jul 31, 2009 at 1:40 PM, ming li<mi...@cs.umass.edu> wrote:
> Hi All,
>
> Does anyone know if RackAwareStrategy is fully functional? I ask
> because RackAwareStrategy picks nodes in different data centers/racks
> first, whereas StorageService.getPredecessor() and
> StorageService.getSuccessor() do not check data center/rack. I am
> wondering if this causes some inconsistency. For instance, suppose
> node A is node B's predecessor in the token space and they are in the
> same data center. If RackAwareStrategy is used, node A wont replicate
> its data on node B. However, when node B tries to figure out the token
> ranges it is responsible for, it calls StorageService.getPredecessor()
> and finds A is its predecessor and its responsible for A's token
> range.
>
>
> Best,
>
> Ming
>