the intended meaning of "initial" is "use this the first time you
start up; it will be ignored after that, if you use nodetool to move
it around." Sorry for the confusion.
On Tue, Jul 12, 2011 at 12:53 PM, Eric tamme wrote:
> On Tue, Jul 12, 2011 at 3:32 PM, Jonathan Ellis wrote:
>> You're goin
On Tue, Jul 12, 2011 at 3:32 PM, Jonathan Ellis wrote:
> You're going to be mad at how simple the answer turns out to be. :)
>
> Nodes "own" the range from (previous, token], NOT from [token, next).
> So, the last node will get from (50, 75] and the first will get from
> (75, 0].
>
Okay i figured
You're going to be mad at how simple the answer turns out to be. :)
Nodes "own" the range from (previous, token], NOT from [token, next).
So, the last node will get from (50, 75] and the first will get from
(75, 0].
On Tue, Jul 12, 2011 at 9:38 AM, Eric tamme wrote:
> I have been reading through
I have been reading through some code in TokenMetadata.java,
specifically with ringIterator() and firstTokenIndex(). I am trying
to get a very firm grasp on how nodes are collected for writes.
I have run into a bit of confusion about what happens when the data's
token is larger than than the larg
