Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Set the old primary host read_only=0 if failover/switch over failed. #1482

Open
beigithub opened this issue Apr 4, 2023 · 0 comments
Open

Comments

@beigithub
Copy link

Hello:
For graceful switchover, we noticed in some cases, even if the candidate host is lagging, the orchestrator still goes ahead and set read_only=1 on the old primary before lag is noticed. This left the old primary with read_only =1 but switchover didn't happen, human intervention is needed to set read_only=0 on the old primary again. Is there a way to detect the lag and exit the switch-over process "before" setting read_only=1 on the old primary?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant