I am running a MongoDB replica set with several secondaries. All secondaries have closer ping times to the Meteor instance than the primary. All MongoDB instances are in separate physical locations, some with <5ms ping times, some with 130ms times.
I have this when running my Meteor app
Will this tell Meteor to write to the Primary and read from the CLOSEST Secondary based on ping times? server1 (furthest away) is the Primary. Server 2 and 3 are in separate places.
If the closest mongo Secondary goes down, will Meteor automatically start using the next mongo Secondary?