-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
ALL
-
16
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.
- related to
-
SERVER-39621 Disabled chaining should enforce sync source change when the primary steps down even if the oplog fetcher isn't killed on sync source
- Closed