Created https://issues.apache.org/jira/browse/CASSANDRA-3400
Thanks for your help, Scott Fines ________________________________________ From: Sylvain Lebresne [sylv...@datastax.com] Sent: Monday, October 24, 2011 11:37 AM To: user@cassandra.apache.org Subject: Re: ConcurrentModificationException during nodetool repair On Mon, Oct 24, 2011 at 6:23 PM, Scott Fines <scott.fi...@nisc.coop> wrote: > Hello all, > Right now, I have 10 machines running Cassandra 0.8.7, and mostly they are > working fine. However, during a nodetool repair of one machine, I'm seeing: > ERROR [AntiEntropySessions:12] 2011-10-24 11:17:52,154 > AbstractCassandraDaemon.java (line 139) Fatal exception in thread > Thread[AntiEntropySessions:12,5,RMI Runtime] > java.lang.RuntimeException: java.util.ConcurrentModificationException > at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:34) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:619) > Caused by: java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) > at java.util.HashMap$KeyIterator.next(HashMap.java:828) > at > org.apache.cassandra.service.AntiEntropyService$RepairSession$RepairJob.sendTreeRequests(AntiEntropyService.java:784) > at > org.apache.cassandra.service.AntiEntropyService$RepairSession.runMayThrow(AntiEntropyService.java:680) > at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:30) > ... 6 more > Is this a situation where I need to perform some other maintenance task > before running a repair? No, that sounds like a bug, do you mind opening a ticket on JIRA (https://issues.apache.org/jira/browse/CASSANDRA) This won't have much consequence except that the repair has failed. But you can restart a new one (hoping you won't get the same problem, but hopefully you won't it looks like a race). > Thanks for your help, > Scott Fines
