Skip to content

Clarify that a recreate won't keep read availability. #2186

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

Jump to bottom
Merged
merged 1 commit into from
Mar 24, 2025
Merged

Clarify that a recreate won't keep read availability. #2186

merged 1 commit into from
Mar 24, 2025

Conversation

tselmegbaasan
Copy link
Contributor

Remove ambiguity that disaster recovery can recover a write unavailable database without causing read unavailability.

@tselmegbaasan
Remove ambiguity that disaster recovery can recover a write unavailab…
61aa5b9 
…le database without causing read unavailability.
@neo-technology-commit-status-publisher
Copy link
Collaborator

neo-technology-commit-status-publisher commented Mar 20, 2025 •
edited
Loading

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

@NataliaIvakina NataliaIvakina self-assigned this Mar 20, 2025
NataliaIvakina
NataliaIvakina approved these changes Mar 24, 2025
View reviewed changes
Copy link
Collaborator

@NataliaIvakina NataliaIvakina left a comment

Choose a reason for hiding this comment

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

@tselmegbaasan, hi! I guess we need to publish this change in current and 5.x versions, right?
I can take care of it.

@NataliaIvakina NataliaIvakina merged commit 6be7c96 into neo4j:dev Mar 24, 2025
8 checks passed
NataliaIvakina pushed a commit to NataliaIvakina/docs-operations that referenced this pull request Mar 24, 2025
@tselmegbaasan @NataliaIvakina
Clarify that a recreate won't keep read availability. (neo4j#2186)
2b7b230 
Remove ambiguity that disaster recovery can recover a write unavailable
database without causing read unavailability.
NataliaIvakina pushed a commit to NataliaIvakina/docs-operations that referenced this pull request Mar 24, 2025
@tselmegbaasan @NataliaIvakina
Clarify that a recreate won't keep read availability. (neo4j#2186)
3012eb9 
Remove ambiguity that disaster recovery can recover a write unavailable
database without causing read unavailability.
NataliaIvakina added a commit that referenced this pull request Mar 24, 2025
@NataliaIvakina @tselmegbaasan
Clarify that a recreate won't keep read availability. (#2186) (#2190)
631a150 
Remove ambiguity that disaster recovery can recover a write unavailable
database without causing read unavailability.

Co-authored-by: Tselmeg Baasan <37698237+tselmegbaasan@users.noreply.github.com>
NataliaIvakina added a commit that referenced this pull request Mar 24, 2025
@NataliaIvakina @tselmegbaasan
Clarify that a recreate won't keep read availability. (#2186) (#2191)
1ecb687 
Remove ambiguity that disaster recovery can recover a write unavailable
database without causing read unavailability.

Co-authored-by: Tselmeg Baasan <37698237+tselmegbaasan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@NataliaIvakina NataliaIvakina NataliaIvakina approved these changes

@AnnaSjerling AnnaSjerling AnnaSjerling approved these changes

Assignees

@NataliaIvakina NataliaIvakina

Labels

cherry-pick-this-to-5.x cherry-pick-this-to-main clustering dev

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@tselmegbaasan @neo-technology-commit-status-publisher @NataliaIvakina @AnnaSjerling