Skip to content
This repository was archived by the owner on Feb 18, 2025. It is now read-only.

Introducing RecoverReadOnlyMaster option, ReadOnlyMaster failure analysis and recovery #1330

Closed
wants to merge 3 commits into from

Conversation

shlomi-noach
Copy link
Collaborator

Fixes #1328

Description

This PR introduces an opt-in behavior: when a replication cluster's primary is found to be read_only, orchestrator analyzes that as a failure scenario and, based on opt-in configuration, spawn a recovery.

This behavior is controlled by the new variable RecoverReadOnlyMaster (defaults false)

…ysis and recovery

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
@shlomi-noach
Copy link
Collaborator Author

I wonder if we should just use NoWriteableMasterStructureWarning as the failure indicator.

…tion treating it as error

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
@shlomi-noach
Copy link
Collaborator Author

Closed in favor of #1332

@shlomi-noach shlomi-noach deleted the analysis-read-only-master branch March 21, 2021 07:16
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Orchestrator to monitor RW status of the primary node.
1 participant