[SERVER-49708] Election with chaining disabled doesn't make node change sync source Created: 17/Jul/20  Updated: 22/Jul/20  Resolved: 22/Jul/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Siyuan Zhou
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
Related
related to SERVER-39621 Disabled chaining should enforce sync... Closed
Operating System: ALL
Participants:
Linked BF Score: 16

 Description   

If a new node becomes primary and we're not allowing chaining, we need to re-evaluate the sync source when we notice the new primary.



 Comments   
Comment by Tess Avitabile (Inactive) [ 22/Jul/20 ]

Sounds good! I've approved the backport, and I'll schedule it after GA.

Comment by Tess Avitabile (Inactive) [ 20/Jul/20 ]

evin.roesle

Comment by Siyuan Zhou [ 20/Jul/20 ]

I think SERVER-39621 is the ticket xuerui.fa mentioned in triage meeting. tess.avitabile, we declined its backport to 4.4. samy.lanka believes the backport to 4.4 should be straightforward. Maybe we can reconsider it?

Generated at Thu Feb 08 05:20:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.