Re: ConcurrentModificationException in gossiper while decommissioning another node

2010-05-19 Thread Ran Tavory
that sounds like it, thanks On Tue, May 18, 2010 at 3:53 PM, roger schildmeijer wrote: > This is hopefully fixed in trunk (CASSANDRA-757 (revision 938597)); > "Replace synchronization in Gossiper with concurrent data structures and > volatile fields." > > // Roger Schildmeijer > > > On Tue, May 1

Re: ConcurrentModificationException in gossiper while decommissioning another node

2010-05-18 Thread roger schildmeijer
This is hopefully fixed in trunk (CASSANDRA-757 (revision 938597)); "Replace synchronization in Gossiper with concurrent data structures and volatile fields." // Roger Schildmeijer On Tue, May 18, 2010 at 1:55 PM, Ran Tavory wrote: > While the node 192.168.252.61 was in the process of decommiss

ConcurrentModificationException in gossiper while decommissioning another node

2010-05-18 Thread Ran Tavory
While the node 192.168.252.61 was in the process of decommissioning I see this error in two other nodes: INFO [Timer-1] 2010-05-18 06:01:12,048 Gossiper.java (line 179) InetAddress /192.168.252.62 is now dead. INFO [GMFD:1] 2010-05-18 06:04:00,189 Gossiper.java (line 568) InetAddress /192.168.25