On Wed, Feb 15, 2012 at 9:25 AM, Rob Coli wrote:
> On Tue, Feb 14, 2012 at 2:02 PM, Franc Carter
> wrote:
>
>> On Wed, Feb 15, 2012 at 8:49 AM, Brandon Williams wrote:
>>
>>> Before 1.0.8, use https://issues.apache.org/jira/browse/CASSANDRA-3337
>>> to remove it.
>>>
>>
>> I'm missing something
On Tue, Feb 14, 2012 at 2:02 PM, Franc Carter wrote:
> On Wed, Feb 15, 2012 at 8:49 AM, Brandon Williams wrote:
>
>> Before 1.0.8, use https://issues.apache.org/jira/browse/CASSANDRA-3337
>> to remove it.
>>
>
> I'm missing something ;-( I don't see a solution in this link . .
>
The solution is a
On Wed, Feb 15, 2012 at 8:49 AM, Brandon Williams wrote:
> Before 1.0.8, use https://issues.apache.org/jira/browse/CASSANDRA-3337
> to remove it.
>
I'm missing something ;-( I don't see a solution in this link . .
cheers
>
> On Tue, Feb 14, 2012 at 3:44 PM, Franc Carter
> wrote:
> >
> > I t
Before 1.0.8, use https://issues.apache.org/jira/browse/CASSANDRA-3337
to remove it.
On Tue, Feb 14, 2012 at 3:44 PM, Franc Carter wrote:
>
> I teminated (ec2 destruction) a node that I was wedged during bootstrap.
> However when I try to removetoken I get 'Token not found'.
>
> It looks a bit li
I teminated (ec2 destruction) a node that I was wedged during bootstrap.
However when I try to removetoken I get 'Token not found'.
It looks a bit like this issue ?
https://issues.apache.org/jira/browse/CASSANDRA-3737
nodetool -h 127.0.0.1 ring gives this
Address DC Rack
;s been in the ring.
>
> So, if I nodetool removetoken forced it, would I still have to be concerned
> about running a repair?
There have probably been some writes that thought that node was part
of the replica set, so you may still be missing a replica in that
regard. If you're
ow, nodetool ring shows this old node:
>>
>> 10.84.73.18 datacenter1 rack1 Down Leaving ? 6.71%
>> 32695837177645752437561450928649262701
>>
>> So I started a nodetool removetoken on
>> 32695837177645752437561450928649262701 last Friday.
ack1 Down Leaving ? 6.71%
> 32695837177645752437561450928649262701
>
> So I started a nodetool removetoken on 32695837177645752437561450928649262701
> last Friday. It's still going strong this morning, on day 5:
>
> ./bin/nodetool -h 10.84.73.47 -p 8080 removetoken status
> RemovalStatus:
ries about failing to write/read to IP 10.84.73.18.
We upgraded to Cassandra 0.8.4. Now, nodetool ring shows this old node:
10.84.73.18 datacenter1 rack1 Down Leaving ? 6.71%
32695837177645752437561450928649262701
So I started a nodetool remo
