java.util.ConcurrentModificationException in Gossiper
-----------------------------------------------------
Key: CASSANDRA-4019
URL: https://issues.apache.org/jira/browse/CASSANDRA-4019
Project: Cassandra
Issue Type: Bug
Components: Core
Affects Versions: 0.8.9
Reporter: Thibaut
Priority: Minor
I have never seen this one before. Might be triggered by a race condition under
heavy load. This error was triggered on 0.8.9
ERROR [GossipTasks:1] 2012-03-05 04:16:55,263 Gossiper.java (line 162) Gossip
error
java.util.ConcurrentModificationException
at java.util.ArrayDeque$DeqIterator.next(ArrayDeque.java:605)
at
org.apache.cassandra.utils.AbstractStatsDeque.sum(AbstractStatsDeque.java:37)
at
org.apache.cassandra.utils.AbstractStatsDeque.mean(AbstractStatsDeque.java:60)
at org.apache.cassandra.gms.ArrivalWindow.mean(FailureDetector.java:259)
at org.apache.cassandra.gms.ArrivalWindow.phi(FailureDetector.java:282)
at
org.apache.cassandra.gms.FailureDetector.interpret(FailureDetector.java:155)
at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:538)
at org.apache.cassandra.gms.Gossiper.access$700(Gossiper.java:57)
at org.apache.cassandra.gms.Gossiper$GossipTask.run(Gossiper.java:157)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
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:662)
INFO [GossipStage:1] 2012-03-05 04:16:55,263 Gossiper.java (line 737) Node
/192.168.3.18 has restarted, now UP again
INFO [GossipStage:1] 2012-03-05 04:16:55,264 Gossiper.java (line 705)
InetAddress /192.168.3.18 is now UP
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
