Noureddine Chatti created CASSANDRA-8537:
--------------------------------------------

             Summary: ConcurrentModificationException while executing 'nodetool 
cleanup'
                 Key: CASSANDRA-8537
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8537
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
         Environment: Debian 7.7, Oracle JRE 1.7.0_72
            Reporter: Noureddine Chatti
             Fix For: 2.1.2


After adding a new node to an existing cluster (7 already started nodes), and 
waiting a few minutes to be sure that data migration to the new node is 
completed, I began to use the command nodetool cleanup sequentially on each old 
node. When I issued this command on the third node, after a few minutes I got a 
ConcurrentModificationException.

~$ nodetool cleanup
error: null
-- StackTrace --
java.util.ConcurrentModificationException
        at java.util.ArrayList$Itr.checkForComodification(Unknown Source)
        at java.util.ArrayList$Itr.next(Unknown Source)
        at 
org.apache.cassandra.db.index.SecondaryIndexManager.deleteFromIndexes(SecondaryIndexManager.java:476)
        at 
org.apache.cassandra.db.compaction.CompactionManager$CleanupStrategy$Full.cleanup(CompactionManager.java:833)
        at 
org.apache.cassandra.db.compaction.CompactionManager.doCleanupOne(CompactionManager.java:704)
        at 
org.apache.cassandra.db.compaction.CompactionManager.access$400(CompactionManager.java:97)
        at 
org.apache.cassandra.db.compaction.CompactionManager$5.execute(CompactionManager.java:370)
        at 
org.apache.cassandra.db.compaction.CompactionManager$2.call(CompactionManager.java:267)
        at java.util.concurrent.FutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to