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
Own-origin recovery: a failover self catch-up entry shares the recovery range's node id on the sender #1404
What happens: on the sender, a failover self catch-up subscription entry (an older receiver asking for its own origin after failover) still lowers the replay start computed from the subscription list, and it names the same node, so it shares a node id in subscribedNodeIds with an own-origin recovery range from a capable receiver (replication/replicationConnection.ts, the loop that finds the earliest start). With both present, the recovery range's per-node entry and the catch-up's start can overwrite each other.
Possible fix: treat the two as mutually exclusive on a capable receiver (drop the failover entry when a recovery range is present), or key the recovery range separately.
Activity