Hi. We’ve been experiencing the problem that when we add a node to a replica set (mongo4.0) from backup files, the application with readPreference=secondary often encounters latency spikes for a period time.
I know cache of the new node is cold, and the reads may be served from disk.
Is this problem solved in mongo 5.0 ? I know there’s Hedged Reads, but not sure whether it can solve the spike problem when a new node is added ?
Maybe we can gradually send requests to the new node when the connections between mongos and mongod are spawned (