Skip to content

DOC-12487 Maintain durable writes #3810

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: release/8.0
Choose a base branch
from
Open

DOC-12487 Maintain durable writes #3810

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
32fb999
Adding what's new changes. Also committing clean up of the DUrability…
ggray-cb May 20, 2025
53fa155
Copyedits.
ggray-cb May 20, 2025
97d9666
Rough draft complete for feature
ggray-cb May 21, 2025
526a91a
Some minor tweaks
ggray-cb May 21, 2025
b02b05d
Last minute tweaks
ggray-cb May 21, 2025
1b5634c
Added What's New anchor
ggray-cb May 21, 2025
cc52598
Fixed typo
ggray-cb May 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions modules/introduction/partials/new-features-80.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -108,6 +108,21 @@ and limits the number of metrics to 100.
Additional information sent by clients at connection time can be found in the logs.


[[new-feature-800-maintain-durable-writes]]
https://jira.issues.couchbase.com/browse/MB-43068[MB-43068] Optionally Maintain Durable Writes During Single Replica Failovers::
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that this title accurately reflects what this does. Things do not behave differently if there is a "Single" failover, or more. "Replica" is somewhat overloaded as we don't fail over replicas. It also does not state what we "Maintain".

Suggest:
"Optionally Maintain Durable Write Availability Without Majority After Failover"

In a bucket with a single replica, you can enable an option named `durabilityImpossibleFallback` that allows durable writes to succeed even when they cannot meet their majority requirements.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not mention the number of replicas

This option is off by default.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can it be changed to:
"This option is off by default."

This is a temporary setting to allow clients to continue to write data when nodes are unavailable due to failovers.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is "temporary" about this setting? I don't think that we have any intent to remove it, and it does not turn itself off.

For example, you can enable this option while you're performing an upgrade using the graceful failover followed by a delta recovery method.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example applies only to the single replica case. If/when you remove the previous references to a single replica, you may wish/need to add that here.

Without this option, the client's durable writes would fail until the servers finished recovery, disrupting your applications.

+
include::learn:partial$maintain-durability-warning.adoc[]

+
See xref:learn:data/durability.adoc#maintaining-durable-writes[Maintaining Durable Writes During Single Replica Failovers] for more information about this feature.


[#section-new-feature-800-XDCR]
=== XDCR
https://jira.issues.couchbase.com/browse/MB-61048[MB-61048]::
Expand Down
Loading