[
https://issues.apache.org/jira/browse/CASSANDRA-17679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17574965#comment-17574965
]
Jeremiah Jordan commented on CASSANDRA-17679:
---------------------------------------------
{quote}All {{-Dcassandra.reset_bootstrap_progress}} seems to do is truncate the
system keyspace of ranges, but none of the already-bootstrapped-data?
{quote}
correct. But I don’t see a proposal here to add truncating? I would definitely
be in favor of adding the ability to remove all existing data before starting
the bootstrap again. All the patch here seems to do is skip looking at the
already streamed ranges, which has the exact same effect as deleting the ranges
from the system table.
I’m not against changing the default behavior. I just don’t like adding new
flags that do the same thing as existing ones. If we want to change the default
behavior and add a new yaml flag to complement the existing -D that seems
reasonable to me.
Also if the main worry here is data redirections then I would suggest adding
that truncation ability in. Because streaming from scratch won’t help your
resurrection problem if someone waits days between retries.
> 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
