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
{{ message }}
Repository navigation
Commit b4572f5
Browse filesBrowse the repository at this point in the historyBrowse files
Read replicas of a master the cluster has declared failed
A replica cut off from its master falls further behind only while
somebody writes to the shard. Once the cluster has agreed the master is
down, nobody does until a new master is elected, so the replicas' data
is the freshest the shard can offer no matter how long ago their links
broke. Excluding them after ReplicaLinkDownTolerance turns a stalled
failover into a read outage for no gain.
The master's state comes from CLUSTER NODES fetched with every reload.
Only the agreed flag counts: a node's own suspicion (fail?) does not,
and without a readable CLUSTER NODES the tolerance alone decides. A
replica that has never synced since it started stays excluded either
way.
0 commit comments