It appears that changing the value of settings.chaininingEnabled does not cause each member of the replica set to re-evaluate it's sync source. It seems reasonable that changing the value of this setting should cause each member to re-evaluate it's sync source and (if necessary) choose a sync source in accordance with the new value.
- 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