cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jon Travis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5836) Seed nodes should be able to bootstrap without manual intervention
Date Thu, 14 Aug 2014 21:00:18 GMT


Jon Travis commented on CASSANDRA-5836:

I was just bitten by this as well.  Our ops uses ZooKeeper to store a list of all our infrastructure,
so I wrote a SeedProvider that peeked into Zk for the list of Cassandra nodes and returned
that as the seed list ... big mistake..   Our push-button deployment launched the node (it
thought it was a seed), so it essentially stopped doing anything, reported errors of missing
keyspaces and column families, then simply sat there.  All the while, it claims it has a portion
of the ring, yet no data. 

There is no good documentation about this and no warnings in the logs -- this is certainly
something that will bite more people.  It would be nice if the process could warn about the
error or refuse to start under this scenario.  

> Seed nodes should be able to bootstrap without manual intervention
> ------------------------------------------------------------------
>                 Key: CASSANDRA-5836
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Bill Hathaway
>            Priority: Minor
> The current logic doesn't allow a seed node to be bootstrapped.  If a user wants to bootstrap
a node configured as a seed (for example to replace a seed node via replace_token), they first
need to remove the node's own IP from the seed list, and then start the bootstrap process.
 This seems like an unnecessary step since a node never uses itself as a seed.
> I think it would be a better experience if the logic was changed to allow a seed node
to bootstrap without manual intervention when there are other seed nodes up in a ring.

This message was sent by Atlassian JIRA

View raw message