[
https://issues.apache.org/jira/browse/CASSANDRA-2447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis reopened CASSANDRA-2447:
---------------------------------------
I forgot that we ammended bootstrap to wait for SLB.BROADCAST_INTERVAL as well
as RING_DELAY. This is silly; it won't matter if we bootstrap based on current
load (as propagated by gossip from last "broadcast") or wait another minute for
another broadcast. And if you are bootstrapping before any load has been
gossipped? It will pick a random token, but I'm okay with that because (1) you
shouldn't be letting autobootstrap pick the token in the first place and (2)
the workaround is simple: wait until your cluster has been up 60s before
bootstrapping more nodes.
v2 attached that fixes this and also amends tests to not wait the full
ring_delay.
> Remove auto-bootstrap option
> ----------------------------
>
> Key: CASSANDRA-2447
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2447
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 1.0
>
> Attachments: 2447-v2.txt
>
>
> We already optimize auto-bootstrap to be no-op if there are no non-system
> tables.
> Given that, the only penalty imposed by autobootstrap is a 30s sleep waiting
> for gossip. Feels worth it to avoid the confusion this option causes, and
> the problems if you don't turn it on when it should be.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
