[
https://issues.apache.org/jira/browse/CASSANDRA-757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12842845#action_12842845
]
Jonathan Ellis commented on CASSANDRA-757:
------------------------------------------
i think what needs to happen is take all the structures in Gossiper and make
them Concurrent equivalents, encapsulate any places where we're returning them
to other objects directly, and audit the rest for correctness, because the
original author basically ignored threadsafety entirely
> FatClient removal causes ConcurrentModificationException
> --------------------------------------------------------
>
> Key: CASSANDRA-757
> URL: https://issues.apache.org/jira/browse/CASSANDRA-757
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.5
> Environment: debian lenny amd64 OpenJDK 64-Bit Server VM (build
> 1.6.0_0-b11, mixed mode)
> Reporter: Brandon Williams
> Assignee: Jaakko Laine
> Priority: Minor
> Fix For: 0.7
>
> Attachments: 757.txt
>
>
> After using a fatclient and killing it, I later receive this ST on all nodes:
> INFO 16:04:58,999 FatClient /10.242.4.13 has been silent for 3600000ms,
> removing from gossip
> ERROR 16:04:58,999 Fatal exception in thread Thread[Timer-1,5,main]
> java.lang.RuntimeException: java.util.ConcurrentModificationException
> at
> org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:96)
> at java.util.TimerThread.mainLoop(Timer.java:534)
> at java.util.TimerThread.run(Timer.java:484)
> Caused by: java.util.ConcurrentModificationException
> at java.util.Hashtable$Enumerator.next(Hashtable.java:1048)
> at org.apache.cassandra.gms.Gossiper.doStatusCheck(Gossiper.java:382)
> at
> org.apache.cassandra.gms.Gossiper$GossipTimerTask.run(Gossiper.java:90)
> ... 2 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
