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

Paulo Motta commented on CASSANDRA-17679:
-----------------------------------------

I agree this feature is useful to some users and we should keep it. 

Since there are known edge cases and limitations, my proposal is to disable 
this feature by default on 4.0+ (with proper notice on NEWS.txt), by simply 
setting "-Dcassandra.reset_bootstrap_progress=true" by default, until we work 
on making the feature more reliable. I think now it's too late to change 
default behavior on 3.x so we can keep it as it is.

It would be nice to make "-Dcassandra.reset_bootstrap_progress=true" clear 
existing bootstrap data as it would make this feature more reliable. Not sure 
if this should be done in this ticket together with disabling this feature by 
default or as a separate effort.

> 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

Reply via email to