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

[jira] [Commented] (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=17624610#comment-17624610 ] 

Josh McKenzie commented on CASSANDRA-17679:
-------------------------------------------

Circling back to this.

Have a patch in a place where I'm happy with it + happy w/changes to dtest. What I am _not_ happy with is that the added in-jvm dtest to confirm exception thrown on resume with data found but no config param specified is flaking in the regular in-jvm dtest runtime but _not_ flaking in the multiplexer. Or reproducing locally.

So I'll chew on that for a bit, but for posterity here's where we are (in case you're curious [~paulo])

 ||Item|Link||
|C* PR|[link|https://github.com/apache/cassandra/pull/1952]|
|dtest branch|[link|https://github.com/josh-mckenzie/cassandra-dtest/commit/0ab0701522730f9cc26e08d475e565d03a24c624]|
|Pre-commit CI|[link|https://app.circleci.com/pipelines/github/josh-mckenzie/cassandra/321/workflows/6f697fe3-194b-4177-8781-ef859b3d7163]|

> 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: 20m
>  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