[
https://issues.apache.org/jira/browse/CASSANDRA-8591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Smith updated CASSANDRA-8591:
------------------------------------
Priority: Minor (was: Major)
> Tunable bootstrapping
> ---------------------
>
> Key: CASSANDRA-8591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8591
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Donald Smith
> Priority: Minor
>
> Often bootstrapping fails due to errors like "unable to find sufficient
> sources for streaming range". But cassandra is supposed to be fault tolerant,
> and it's supposed to have tunable consistency.
> If it can't find some sources, it should allow bootstrapping to continue,
> under control by parameters (up to 100 failures, for example), and should
> print out a report about what ranges were missing. For many apps, it's far
> better to bootstrap what's available then to fail flat.
> Same with rebuilds.
> We were doing maintenance on some disks and when we started back up, some
> nodes ran out of disk space, due to operator miscaluculation. Thereafter,
> we've been unable to bootstrap new nodes, due to "unable to find sufficient
> sources for streaming range." But bootstrapping with partial success would
> be far better than being unable to bootstrap at all, and cheaper than a
> repair. Our consistency requirements are low but not zero.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
