[SERVER-26398] Secondary can refuse to sync from primary that is ahead of it, preventing it from ever rolling back Created: 29/Sep/16  Updated: 06/Dec/22  Resolved: 30/Sep/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Replication
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

If a secondary has no sync source, but there is a valid primary it can/should be syncing from, but that primary has an older optime than it does, the secondary will never select a sync source, and thus will never go into rollback as it should.



 Comments   
Comment by Spencer Brody (Inactive) [ 30/Sep/16 ]

This is works as designed. Rollback is triggered when the primary is ahead of the secondary, but with a different view of the history (ie the primary has writes the secondary doesn't and the secondary has writes the primary doesn't)

Generated at Thu Feb 08 04:11:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.