Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: Single Node Cassandra Installation
From: Drew Kutcharian <drew@venarc.com>
In-Reply-To: 
 <CACHzRHa87apkP6edLcds6VGCotf46YAqcd4pm1a3qJateJ02VQ@mail.gmail.com>
Date: Sat, 10 Nov 2012 18:16:24 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <00E337E7-6418-4281-A84D-8FF9EB03DA21@venarc.com>
References: <CCBD4066.18D0D%mkjellman@barracuda.com>
 <7D4DD5A8-3AF8-4EA6-A186-0BD921C540C1@venarc.com>
 <CACHzRHa87apkP6edLcds6VGCotf46YAqcd4pm1a3qJateJ02VQ@mail.gmail.com>
To: user@cassandra.apache.org

Thanks Rob, this makes sense. We only have one rack at this point, so I =
think it'd be better to start with PropertyFileSnitch to make Cassandra =
think that these nodes each are in a different rack without having to =
put them on different subnets. And I will have more flexibility (at the =
cost of keeping the property file in sync) when it comes to growth. What =
do you think?

-- Drew


On Nov 5, 2012, at 7:50 PM, Rob Coli <rcoli@palominodb.com> wrote:

> On Mon, Nov 5, 2012 at 12:23 PM, Drew Kutcharian <drew@venarc.com> =
wrote:
>>> Switching from SimpleStrategy to RackAware can be a pain.
>>=20
>> Can you elaborate a bit? What would be the pain point?
>=20
> If you don't maintain the same replica placement vis a vis nodes on
> your cluster, you have to dump and reload.
>=20
> Simple example, 6 node cluster RF=3D3 :
>=20
> SimpleSnitch : A B C D E F
>=20
> Data for natural range of A is also on B and C, the "next" nodes in =
the ring.
>=20
> RackAwareSnitches : A B C D E F
> "racks" they are in  :  1 1  2  2 3 3
>=20
> Data for natural range of A is also on C and E, because despite not
> being the next nodes in the RING, they are the first nodes in the next
> rack.
>=20
> If however you go from simple to rack aware and put your nodes in =
racks like :
>=20
> A B C D E F
> 1 2 3 1 2 3
>=20
> Then you have the same replica placement that SimpleStrategy gives you
> and can safely switch strategies/snitches on an existing cluster. Data
> for A is on B and C, on the same hosts, but for different reasons. Use
> nodetool getendpoints to test.
>=20
> =3DRob
>=20
> --=20
> =3DRobert Coli
> AIM&GTALK - rcoli@palominodb.com
> YAHOO - rcoli.palominob
> SKYPE - rcoli_palominodb