cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thibaut (Created) (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-4019) java.util.ConcurrentModificationException in Gossiper
Date Thu, 08 Mar 2012 10:48:57 GMT
java.util.ConcurrentModificationException in Gossiper

                 Key: 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 (line 162) Gossip error
        at java.util.ArrayDeque$
        at org.apache.cassandra.utils.AbstractStatsDeque.sum(
        at org.apache.cassandra.utils.AbstractStatsDeque.mean(
        at org.apache.cassandra.gms.ArrivalWindow.mean(
        at org.apache.cassandra.gms.ArrivalWindow.phi(
        at org.apache.cassandra.gms.FailureDetector.interpret(
        at org.apache.cassandra.gms.Gossiper.doStatusCheck(
        at org.apache.cassandra.gms.Gossiper.access$700(
        at org.apache.cassandra.gms.Gossiper$
        at java.util.concurrent.Executors$
        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(
        at java.util.concurrent.FutureTask.runAndReset(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(
        at java.util.concurrent.ScheduledThreadPoolExecutor$
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
        at java.util.concurrent.ThreadPoolExecutor$
 INFO [GossipStage:1] 2012-03-05 04:16:55,263 (line 737) Node /
has restarted, now UP again
 INFO [GossipStage:1] 2012-03-05 04:16:55,264 (line 705) InetAddress /
is now UP

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message