You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Anne Sullivan (JIRA)" <ji...@apache.org> on 2013/12/10 21:40:08 UTC

[jira] [Commented] (CASSANDRA-5836) Seed nodes should be able to bootstrap without manual intervention

    [ https://issues.apache.org/jira/browse/CASSANDRA-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13844643#comment-13844643 ] 

Anne Sullivan commented on CASSANDRA-5836:
------------------------------------------

For ease of maintenance and because we'll likely have many deployments where the cluster size is very small (2 - 5 nodes), I'm wondering if I can set my seed_provider list to contain all nodes except the local node's IP.  ie) For nodes A-C
A-> B, C
B-> A, C
C-> A, B

I think my question is more or less In line with Robert's comment, I'm wondering if satisfying ONLY 2) is safe:

Datastax docs suggest that "every node should have the same list of seeds", and also "To prevent partitions in gossip communications, use the same list of seed nodes in all nodes in a cluster".  In my case, I wouldn't end up with gossip partitions in the example above, so if that's the only reason for the recommendation of keeping the list consistent across all nodes then it should be ok.  

I would like to have all nodes auto-bootstrap, so I can automate the deployment process, push the config once and forget about it.  When adding a new node, I don't want to do 2 edits to the config file (first start without node as seed, then add node as seed). 

> Seed nodes should be able to bootstrap without manual intervention
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-5836
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5836
>             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
(v6.1.4#6159)