Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 74.125.82.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=Gl65Q0e0I2KO5+br9gIYv/zogb1l/2dP1fyhWwF9j+g3Ox6KzdvynGQzgHobiFF7sq
         HQTo1j+Rxmo4jc2l5gVz360009xGvL/QwlEJ9j3pcUYwlKqbh2EgQP2aipfDt9nc4LBQ
         2eO1yuEWoNpt65YQcsm0GFPyEixND4Z3lI3CE=
MIME-Version: 1.0
In-Reply-To: <htf5ev$e3b$1@dough.gmane.org>
References: <htf5ev$e3b$1@dough.gmane.org>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Mon, 24 May 2010 20:24:01 -0500
Message-ID: <AANLkTimgPVjaxWwXcgG-fOogHH0NXZzVMyGJhlx1g_LJ@mail.gmail.com>
Subject: Re: Different KeySpaces for different nodes in the same ring
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

DatacenterShardSnitch in 0.7 allows something like this:

#   DatacenterShardStrategy is a generalization of RackAwareStrategy.
#   For each datacenter, you can specify (in `datacenter.properties`)
#   how many replicas you want on a per-keyspace basis.  Replicas are
#   placed on different racks within each DC, if possible.

(DSS is present in 0.6 but incomplete, which is why it is not documented th=
ere.)

On Mon, May 24, 2010 at 7:26 PM, Mishail <mishail.mishail@gmail.com> wrote:
> Greetings,
>
> Is it possible to spread the particular keyspace only to the part of the
> ring?
>
> For example:
>
> Node =A0 =A0| Keyspaces
> --------------------
> node1 =A0 | KS1
> node2 =A0 | KS2
> node3 =A0 | KS1, KS2
>
> Each KeySpace has ReplicationFactor =3D=3D 2, so, node3 would store data
> from all keyspaces.
>
>


--=20
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com