cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-4850) RuntimeException when bootstrapping a node without an explicitely set token
Date Tue, 23 Oct 2012 13:23:13 GMT
Sylvain Lebresne created CASSANDRA-4850:

             Summary: RuntimeException when bootstrapping a node without an explicitely set
                 Key: CASSANDRA-4850
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.0 beta 1
            Reporter: Sylvain Lebresne
             Fix For: 1.2.0 beta 2

Trying to boostrap a node for which no initial token has been set result in:
java.lang.RuntimeException: No other nodes seen!  Unable to bootstrap.If you intended to start
a single-node cluster, you should make sure your broadcast_address (or listen_address) is
listed as a seed.  Otherwise, you need to determine why the seed being contacted has no knowledge
of the rest of the cluster.  Usually, this can be solved by giving all nodes the same seed
	at org.apache.cassandra.dht.BootStrapper.getBootstrapSource(
	at org.apache.cassandra.dht.BootStrapper.getBalancedToken(
	at org.apache.cassandra.dht.BootStrapper.getBootstrapTokens(
	at org.apache.cassandra.service.StorageService.joinTokenRing(
	at org.apache.cassandra.service.StorageService.initServer(
	at org.apache.cassandra.service.StorageService.initServer(
	at org.apache.cassandra.service.CassandraDaemon.setup(
	at org.apache.cassandra.service.CassandraDaemon.activate(
	at org.apache.cassandra.service.CassandraDaemon.main(

This has been broken by CASSANDRA-4416. More specifically, now that we storage the system
metadata in the schema on startup, the check
                // if we see schema, we can proceed to the next check directly
                if (!Schema.instance.getVersion().equals(Schema.emptyVersion))
                    logger.debug("got schema: {}", Schema.instance.getVersion());
in StorageService.joinTokenRing is broken. This result in the node trying to check the Load
map to pick a token before any gossip state has been received.

Note sure what is the best fix (an easy would be to always wait RING_DELAY before attempting
to pick the token, at least in the case where an initial token isn't set, but that's a big

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:

View raw message