[
https://issues.apache.org/jira/browse/CASSANDRA-17679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17579774#comment-17579774
]
Jeremiah Jordan commented on CASSANDRA-17679:
---------------------------------------------
{quote}That about cover it?
{quote}
Yes.
On the proposal by Paulo. I think we should not change anything for 4.0. But
for 4.1+ I think the proposed setup is a good way forward.
{quote}a) {{-Dcassandra.reset_bootstrap_progress=<unset>}} new default behavior
- fail bootstrap if a previous bootstrap attempt was detected (user needs to
manually cleanup bootstrap progress).
b) {{-Dcassandra.reset_bootstrap_progress=true}} clear streamed ranges from
system.available_ranges, and in the future also cleanup incomplete bootstrap
data on disk (perform this later action in a follow-up ticket)
c) {{-Dcassandra.reset_bootstrap_progress=false}} current default behavior of
skipping already available ranges during bootstrap streaming.
{quote}
If we detect a failed bootstrap then we make the user specify what they want to
do.
Something else to consider is what to do with "nodetool rebuild". It also uses
the data from the progress table. But that as well as trying to remove
existing data are probably worth a new ticket.
> Make resumable bootstrap feature optional
> -----------------------------------------
>
> Key: CASSANDRA-17679
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17679
> Project: Cassandra
> Issue Type: New Feature
> Components: Consistency/Streaming
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 4.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> From the patch I'm working on:
> {code}
> # In certain environments, operators may want to disable resumable bootstrap
> in order to avoid potential correctness
> # violations or data loss scenarios. Largely this centers around nodes going
> down during bootstrap, tombstones being
> # written, and potential races with repair. By default we leave this on as
> it's been enabled for quite some time,
> # however the option to disable it is more palatable now that we have zero
> copy streaming as that greatly accelerates
> # bootstraps. This defaults to true.
> # resumable_bootstrap_enabled: true
> {code}
> Not really a great fit for guardrails as it's less a "feature to be toggled
> on and off" and more a subset of a specific feature that in certain
> circumstances can lead to issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
