-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.4, v4.2
-
Repl 2020-03-09, Repl 2020-03-23
-
(copied to CRM)
Our current implementation of choosing a sync source for initial sync as well as steady state sync could be improved to include preferences provided by the user for situations including:
- not wanting to sync from the primary to mitigate impact to production applications that are targeting the primary
- preference to sync from a node on the same LAN vs having multiple nodes make the trip across the WAN (even if ping times would dictate otherwise)
- syncing from a specific node based on specific user preference
If the preference is not specified or can not be accommodated then we should fall back to choosing based on latency and currency as we do today.
It would be helpful for the specification of a sync source preference to be part of the replica set configuration so it is easily noticed and easily managed. The log should reflect the preference and the reason it was overridden when need be.
- is related to
-
SERVER-47056 Do not use readOnce cursors for collection scan in initial sync
- Closed
- related to
-
SERVER-31487 Replace replSetSyncFrom resync option with initialSyncSource server parameter
- Closed
-
SERVER-44272 Resync data on replSetSyncFrom during initial sync
- Closed