You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by ruslan usifov <ru...@gmail.com> on 2011/04/11 15:15:16 UTC

Cassandra constantly nodes which doens allredy exists

Hello

I use cassandra 0.7.4. After reconfiguring cluster on one node i constantly
see folow log:

INFO [GossipStage:1] 2011-04-11 17:14:13,514 StorageService.java (line 865)
Removing token 56713727820156410577229101238628035242 for /10.32.59.202
INFO [ScheduledTasks:1] 2011-04-11 17:14:13,514 HintedHandOffManager.java
(line 210) Deleting any stored hints for 10.32.59.202


But node 10.32.59.202 doesn't exists alredy. How to prevent this?

Re: Cassandra constantly nodes which doens allredy exists

Posted by ruslan usifov <ru...@gmail.com>.
2011/4/12 aaron morton <aa...@thelastpickle.com>

> In JConsole go to o.a.c.db.HintedHandoffManager and try the
> deleteHintsForEndpopints operation.
>
> This is also called as when a token is removed from the ring, or when a
> node is decomissioned.
>
> What process did you use to reconfigure the cluster?
>
>
I decommission node, then step by step restart all nodes in clustrer. When I
repeat restart operation twice this LOG entry disappear

Re: Cassandra constantly nodes which doens allredy exists

Posted by aaron morton <aa...@thelastpickle.com>.
In JConsole go to o.a.c.db.HintedHandoffManager and try the deleteHintsForEndpopints operation. 

This is also called as when a token is removed from the ring, or when a node is decomissioned. 

What process did you use to reconfigure the cluster?

Aaron

On 12 Apr 2011, at 01:15, ruslan usifov wrote:

> Hello
> 
> I use cassandra 0.7.4. After reconfiguring cluster on one node i constantly see folow log:
> 
> INFO [GossipStage:1] 2011-04-11 17:14:13,514 StorageService.java (line 865) Removing token 56713727820156410577229101238628035242 for /10.32.59.202
> INFO [ScheduledTasks:1] 2011-04-11 17:14:13,514 HintedHandOffManager.java (line 210) Deleting any stored hints for 10.32.59.202
> 
> 
> But node 10.32.59.202 doesn't exists alredy. How to prevent this?
>