Skip to content
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.

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

Bug Report: PRS getting stuck due to a momentary network glitch #17709

Open
GuptaManan100 opened this issue Feb 6, 2025 · 0 comments · May be fixed by #17763
Open

Bug Report: PRS getting stuck due to a momentary network glitch #17709

GuptaManan100 opened this issue Feb 6, 2025 · 0 comments · May be fixed by #17763

Comments

@GuptaManan100
Copy link
Member

Overview of the Issue

It has been observed that after a PRS started, if the last outstanding write on the current primary succeeds but the semi-sync ACKs for the write are lost due to a momentary glitch in the network, DemotePrimary gets blocked on trying to run set super_read_only=true because the last write is still waiting for semi-sync ACKs, even though both the replicas already have it.

This causes PRS to be blocked and eventually time out.

Reproduction Steps

  1. Run PRS, and simulate a network error somehow

Binary Version

main

Operating System and Environment details

-

Log Fragments

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

Successfully merging a pull request may close this issue.

1 participant