Re: nodetool decommission unable to do its job successfully

[aaron morton <aa...@thelastpickle.com>]

Do you have the full stack trace and maybe a few log lines before and after ? Also what version are you using ? 

As a work around you can shutdown the leaving node and use nodetool removetoken from one of the others. 

Cheers

-----------------
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com

On 1/03/2012, at 4:48 AM, Aditya Gupta wrote:

> I ran nodetool decommission on a node from a 4 nodes cluster as follows:
> nodetool -h 192.168.26.130 decommission 
> 
> 
> But it never completes & doesn't show any messages, on seeing the logs I noticed:
> java.util.concurrent.RejectedExecutionException: ThreadPoolExecutor has shut down
> at org.apache.cassandra.concurrent.DebuggableThreadPoolExecutor$1.rejectedExecution(DebuggableThreadPoolExecutor.java:60)
> at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:767)
> at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecuto r.java:658)
> 
> 
> on viewing netstats on this node I can see the node in LEAVING mode 
> mode: LEAVING
> Nothing streaming to /192.168.26.131
> Nothing streaming to /192.168.26.129
> 
> Not receiving any streams.
> 
>