[
https://issues.apache.org/jira/browse/CASSANDRA-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-603.
--------------------------------------
Resolution: Fixed
Thanks for the explanation. Committed, w/ parts of the above as comments to
TokenMetadata.
One minor quibble is, I'd really prefer to avoid having this circular TM <->
ReplicationStrategy dependency cycle. (Which is part of the reason the code
was structured the way it was: RS would pass TM the info it needed to do its
thing in a concurrency-safe fashion, w/o needing to reach into RS itself which
makes auditing for thread-safety much harder). So if you think of a way to
refactor that, even better. :)
> pending range collision between nodes
> -------------------------------------
>
> Key: CASSANDRA-603
> URL: https://issues.apache.org/jira/browse/CASSANDRA-603
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.5
> Reporter: Chris Goffinet
> Fix For: 0.5
>
> Attachments: 603.patch
>
>
> We bootstrapped 5 nodes on the east coast from an existing cluster (5) on
> west. We waited at least 60 seconds before starting up each node so it would
> start bootstrapping. We started seeing these types of errors:
> INFO [GMFD:1] 2009-12-04 01:45:42,065 Gossiper.java (line 568) Node
> /X.X.X.140 has now joined.
> ERROR [GMFD:1] 2009-12-04 01:46:14,371 DebuggableThreadPoolExecutor.java
> (line 127) Error in ThreadPoolExecutor
> java.lang.RuntimeException: pending range collision between /X.X.X.139 and
> /X.X.X.140
> at
> org.apache.cassandra.locator.TokenMetadata.addPendingRange(TokenMetadata.java:242)
> at
> org.apache.cassandra.service.StorageService.updateBootstrapRanges(StorageService.java:481)
> at
> org.apache.cassandra.service.StorageService.onChange(StorageService.java:402)
> at
> org.apache.cassandra.gms.Gossiper.doNotifications(Gossiper.java:692)
> at
> org.apache.cassandra.gms.Gossiper.applyApplicationStateLocally(Gossiper.java:657)
> at
> org.apache.cassandra.gms.Gossiper.applyStateLocally(Gossiper.java:610)
> at
> org.apache.cassandra.gms.GossipDigestAckVerbHandler.doVerb(Gossiper.java:978)
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:38)
> 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:619)
> ERROR [GMFD:1] 2009-12-04 01:46:14,378 CassandraDaemon.java (line 71) Fatal
> exception in thread Thread[GMFD:1,5,main]
> java.lang.RuntimeException: pending range collision between /X.X.X.139 and
> /X.X.X.140
> java.lang.RuntimeException: pending range collision between /X.X.X.139 and
> /X.X.X.140
> at
> org.apache.cassandra.locator.TokenMetadata.addPendingRange(TokenMetadata.java:242)
> at
> org.apache.cassandra.service.StorageService.updateBootstrapRanges(StorageService.java:481)
> at
> org.apache.cassandra.service.StorageService.onChange(StorageService.java:402)
> at
> org.apache.cassandra.gms.Gossiper.doNotifications(Gossiper.java:692)
> at
> org.apache.cassandra.gms.Gossiper.applyApplicationStateLocally(Gossiper.java:657)
> at
> org.apache.cassandra.gms.Gossiper.applyStateLocally(Gossiper.java:610)
> at
> org.apache.cassandra.gms.GossipDigestAckVerbHandler.doVerb(Gossiper.java:978)
> at
> org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:38)
> 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:619)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
