You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Lu Ming (JIRA)" <ji...@apache.org> on 2010/06/30 09:16:52 UTC
[jira] Updated: (CASSANDRA-1239) GossipTimerTask throws
ConcurrentModificationException after node decommission
[ https://issues.apache.org/jira/browse/CASSANDRA-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lu Ming updated CASSANDRA-1239:
-------------------------------
Description:
Yesterday I made decommission for a cassandra node, and this morning the GossipTimerTask threads of all nodes get the fatal exception and crash.
Gossiper.doStatusCheck() visits endPointStateMap_ and get a ConcurrentModificationException when Gossiper.removeEndPoint() is calling
INFO [Timer-0] 2010-06-30 07:53:51,290 Gossiper.java (line 401) FatClient /222.222.111.111 has been silent for 3600000ms, removing from gossip
ERROR [Timer-0] 2010-06-30 07:53:51,291 CassandraDaemon.java (line 78) Fatal exception in thread Thread[Timer-0,5,RMI Runtime]
java.lang.RuntimeException: java.util.ConcurrentModificationException
at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:97)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:382)
at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:91)
... 2 more
was:
Yesterday I made decommission for a cassandra node, and this morning all the GossipTimerTask threads get the fatal exception and crash.
Gossiper.doStatusCheck() visits endPointStateMap_ and get a ConcurrentModificationException when Gossiper.removeEndPoint() is calling
INFO [Timer-0] 2010-06-30 07:53:51,290 Gossiper.java (line 401) FatClient /222.222.111.111 has been silent for 3600000ms, removing from gossip
ERROR [Timer-0] 2010-06-30 07:53:51,291 CassandraDaemon.java (line 78) Fatal exception in thread Thread[Timer-0,5,RMI Runtime]
java.lang.RuntimeException: java.util.ConcurrentModificationException
at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:97)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: java.util.ConcurrentModificationException
at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:382)
at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:91)
... 2 more
> GossipTimerTask throws ConcurrentModificationException after node decommission
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-1239
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1239
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6.2, 0.6.3
> Reporter: Lu Ming
>
> Yesterday I made decommission for a cassandra node, and this morning the GossipTimerTask threads of all nodes get the fatal exception and crash.
> Gossiper.doStatusCheck() visits endPointStateMap_ and get a ConcurrentModificationException when Gossiper.removeEndPoint() is calling
> INFO [Timer-0] 2010-06-30 07:53:51,290 Gossiper.java (line 401) FatClient /222.222.111.111 has been silent for 3600000ms, removing from gossip
> ERROR [Timer-0] 2010-06-30 07:53:51,291 CassandraDaemon.java (line 78) Fatal exception in thread Thread[Timer-0,5,RMI Runtime]
> java.lang.RuntimeException: java.util.ConcurrentModificationException
> at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:97)
> at java.util.TimerThread.mainLoop(Timer.java:512)
> at java.util.TimerThread.run(Timer.java:462)
> Caused by: java.util.ConcurrentModificationException
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1031)
> at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:382)
> at org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:91)
> ... 2 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.