Details
-
New Feature
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
None
Description
We find that we need to "throttle" our writes while ensuring that we don't negatively impact reads on our secondaries. We are working on monitoring qr, lock% and replication lag as part of a replica set "health check" method. Only once the "health check" returns a positive result will we process the updates (or deletes) to Mongo. This will ensure that we don't overwhelm the oplog with a bunch of writes that then (via high lock contention) slow down reads so much that our jbosses start to run out of threads.
Instead of creating this method in our code and then calling it throughout our entire application, it would be ideal if we could make this a configuration of the driver that we set once and use throughout the entire application.