'Controlling the syncSourceHost of a MongoDb replica set
We have a high-end replica set cluster with several members.
The primary is very loaded, so we enabled the chaining settings which enable members to sync from a secondary member.
Our problem is that once in a while the secondary gets very loaded (we use it for queries) and then the other members suffer from high replication lags.
I was wondering if there is a way to control the syncSourceHost in a way that a specific member will be chosen? or is there in general a good approach for solving it?
From reading https://www.mongodb.com/docs/manual/core/replica-set-sync/#std-label-replica-set-replication-sync-source-selection it seems the process is mostly automatic and doesn't provide much control on the source election.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|