[ https://issues.apache.org/jira/browse/CASSANDRA-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13712146#comment-13712146 ]
Andy Cobley commented on CASSANDRA-5768: ---------------------------------------- Jason, You code for build list should read: {code} private void buildSeedsList() { Set<InetAddress> seeds = DatabaseDescriptor.getSeeds(); for (InetAddress seed : seeds) { if (seed.equals(FBUtilities.getBroadcastAddress()) && seeds.size() == 1) seedContacted = true; else seeds.add(seed); } } {code} Sadly that throws an exception at startup: {noformat} ERROR 09:58:35,896 Exception encountered during startup java.lang.UnsupportedOperationException at com.google.common.collect.ImmutableCollection.add(ImmutableCollection.java:92) at org.apache.cassandra.gms.Gossiper.buildSeedsList(Gossiper.java:1072) at org.apache.cassandra.gms.Gossiper.start(Gossiper.java:1046) at org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:555) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:527) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:426) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:354) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:453) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:496) java.lang.UnsupportedOperationException at com.google.common.collect.ImmutableCollection.add(ImmutableCollection.java:92) at org.apache.cassandra.gms.Gossiper.buildSeedsList(Gossiper.java:1072) at org.apache.cassandra.gms.Gossiper.start(Gossiper.java:1046) at org.apache.cassandra.service.StorageService.joinTokenRing(StorageService.java:555) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:527) at org.apache.cassandra.service.StorageService.initServer(StorageService.java:426) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:354) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:453) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:496) Exception encountered during startup: null ERROR 09:58:35,933 Exception in thread Thread[StorageServiceShutdownHook,5,main] java.lang.NullPointerException at org.apache.cassandra.service.StorageService.stopRPCServer(StorageService.java:310) at org.apache.cassandra.service.StorageService.shutdownClientServers(StorageService.java:359) at org.apache.cassandra.service.StorageService.access$000(StorageService.java:95) at org.apache.cassandra.service.StorageService$1.runMayThrow(StorageService.java:492) at org.apache.cassandra.utils.WrappedRunnable.run(WrappedRunnable.java:28) at java.lang.Thread.run(Thread.java:724) {noformat} > If a Seed can't be contacted, a new node comes up as a cluster of 1 > ------------------------------------------------------------------- > > Key: CASSANDRA-5768 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5768 > Project: Cassandra > Issue Type: Bug > Affects Versions: 2.0 beta 1 > Reporter: Andy Cobley > Assignee: Brandon Williams > Priority: Minor > Fix For: 2.0 beta 2 > > Attachments: 5768.txt > > > Setting up a new test cluster using 2.0.0-beta1 and I noticed the following > behaviour with vnodes turned on. > I bring up one node all well and good. however if I bring up a second node, > that can't contact the first (the first being the seed for the second) after > a short period of time, the second goes ahead and assumes it's the only node > and bootstraps with all tokens. > NOTE also this email from Robert Coli > To: u...@cassandra.apache.org > Obviously if you have defined a seed and cannot contact it, the node should > not start as a cluster of one. I have a to-do list item to file a JIRA on the > subject, but if you wanted to file and link us, that'd be super. :) > Startup trace (from the can't contact the seed messages below). > http://aep.appspot.com/display/ABcWltCES1srzPrj5CkS69-GB8o/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira