[JAVA-638] Configurable throttling at the driver level Created: 05/Sep/12 Updated: 29/Oct/17 Resolved: 29/Oct/17 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Write Operations |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Christopher Price | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| 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. |
| Comments |
| Comment by Jeffrey Yemin [ 29/Oct/17 ] |
|
We haven't seen much appetite for this feature, so closing as Won't Fix for now. We can re-open in the future if there is more demand. |
| Comment by Jeffrey Yemin [ 05/Sep/12 ] |
|
Hi Chris, We've been discussing general recommendations for this class of issues, and we'll get back to you as soon as we have something ready. If this is time-critical, please open up a support issue and we can link this to it. |