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: domain of thong@acunu.com designates
 209.85.210.48 as permitted sender)
MIME-Version: 1.0
Sender: thong@acunu.com
In-Reply-To: 
 <CAM3J1MAmWW_xTUqw5-S4_R2R3WJ8w14dxCoNJA_LNzWtTLjhPw@mail.gmail.com>
References: <1312066348.23385.YahooMailNeo@web130113.mail.mud.yahoo.com>
 <1312158262.30835.YahooMailNeo@web130111.mail.mud.yahoo.com>
 <CAM3J1MAmWW_xTUqw5-S4_R2R3WJ8w14dxCoNJA_LNzWtTLjhPw@mail.gmail.com>
From: Theodore Hong <theo@acunu.com>
Date: Tue, 2 Aug 2011 14:20:50 +0100
Message-ID: 
 <CAM3J1MDdtKuK69+=TJcJGoZOrpgJsn1C9s7PUTMwjaY6CMnNcQ@mail.gmail.com>
Subject: Fwd: How tokens work?
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Rafael Almeida <almeidaraf@yahoo.com> wrote:
> I find it hard to explain that without an example. So, let's say the toke=
n space
> is actually from 0 to 100 and we have 4 nodes (let's do this in order to =
make
> things more manageble). In our example, we have the following initial_tok=
ens:
>
> node A =3D 0
> node B =3D 20
> node C =3D 70
> node D =3D 90
>
> Node A would have 0 - 20 tokens assigned to it (20/100 =3D 20% of the loa=
d). =A0Node
> B would have 70 - 20 =3D 50 tokens assigned to it (50% of the load). Node=
 C would
> have 90 - 70 =3D 20 tokens assigned to it (20% of the load) and, finally,=
 node D
> would have 10% of the tokens assigned to it. See how that works?

That's the general idea, but confusingly, the node's token gives the
LAST key that it is responsible for, not the first. =A0So in your
example the ranges would be:

node A =3D 91 through 0 (10%)
node B =3D 1 through 20 (20%)
node C =3D 21 through 70 (50%)
node D =3D 71 through 90 (20%)

theo