You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Run PRS, and simulate a network error somehow
Binary Version
main
Operating System and Environment details
-
Log Fragments
The text was updated successfully, but these errors were encountered:
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 runset 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
Binary Version
Operating System and Environment details
Log Fragments
The text was updated successfully, but these errors were encountered: