You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paulo Motta (Jira)" <ji...@apache.org> on 2022/07/26 17:42:00 UTC

[jira] [Comment Edited] (CASSANDRA-17679) Make resumable bootstrap feature optional

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

Paulo Motta edited comment on CASSANDRA-17679 at 7/26/22 5:41 PM:
------------------------------------------------------------------

Hi, this seems to be related to CASSANDRA-16290, which was marked a duplicate of CASSANDRA-15264. It seems the same issue happens with decommission (resumable decommission), so we should also probably apply the same fix there.

fwiw I think we should make resumable bootstrap/decommission disabled by default in the next major, since this is the safest behavior.


was (Author: paulo):
Hi, this seems to be related to CASSANDRA-16290, which was a duplicate of CASSANDRA-15264. It seems the same issue happens with decommission (resumable decommission), so we should also probably apply the same fix there.

fwiw I think we should make resumable bootstrap disabled by default in the next major, since this is the safest behavior.

> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org