>> >> Did you forget to run repair?
>> >>
>> >> On Mon, Jun 21, 2010 at 7:02 PM, Joost Ouwerkerk
>> >> wrote:
>> >> > I believe we did nodetool removetoken on nodes that were already down
>> >> > (due
>> >&
>>
> >> On Mon, Jun 21, 2010 at 7:02 PM, Joost Ouwerkerk
> >> wrote:
> >> > I believe we did nodetool removetoken on nodes that were already down
> >> > (due
> >> > to hardware failure), but I will check to make sure. We're running
> >>
k to make sure. We're running
>> > Cassandra
>> > 0.6.2.
>> >
>> > On Mon, Jun 21, 2010 at 9:59 PM, Joost Ouwerkerk
>> > wrote:
>> >>
>> >> Greg, can you describe the steps we took to decommission the nodes?
>> >>
>> &
gt; > On Mon, Jun 21, 2010 at 9:59 PM, Joost Ouwerkerk
> > wrote:
> >>
> >> Greg, can you describe the steps we took to decommission the nodes?
> >>
> >> -- Forwarded message --
> >> From: Rob Coli
> >> Date: Mon, Jun 21
10 at 9:59 PM, Joost Ouwerkerk
> wrote:
>>
>> Greg, can you describe the steps we took to decommission the nodes?
>>
>> -- Forwarded message --
>> From: Rob Coli
>> Date: Mon, Jun 21, 2010 at 8:08 PM
>> Subject: Re: get_range_slices confus
010 at 8:08 PM
>> Subject: Re: get_range_slices confused about token ranges after
>> decommissioning a node
>> To: user@cassandra.apache.org
>>
>>
>> On 6/21/10 4:57 PM, Joost Ouwerkerk wrote:
>>
>>> We're seeing very strange behaviour after decomm
he nodes?
>
>
> -- Forwarded message --
> From: Rob Coli
> Date: Mon, Jun 21, 2010 at 8:08 PM
> Subject: Re: get_range_slices confused about token ranges after
> decommissioning a node
> To: user@cassandra.apache.org
>
>
> On 6/21/10 4:57 PM, Joost Ouwerk
On 6/21/10 4:57 PM, Joost Ouwerkerk wrote:
We're seeing very strange behaviour after decommissioning a node: when
requesting a get_range_slices with a KeyRange by token, we are getting
back tokens that are out of range.
What sequence of actions did you take to "decommission" the node? What
ver
We're seeing very strange behaviour after decommissioning a node: when
requesting a get_range_slices with a KeyRange by token, we are getting back
tokens that are out of range.
As a result, ColumnFamilyRecordReader gets confused, since it uses the last
token from the result set to set the start tok
