[SERVER-74671] Require Customers to Set an Explicit Write Concern for Secondary Throttle Created: 07/Mar/23 Updated: 27/Apr/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Panton | Assignee: | Matt Panton |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
Today Currently customer can enable a secondary throttle in two different ways. 1. The customer can set secondary throttle to true in config.settings
2. The customer can set secondary throttle with a explicit write concern in config.settings
Future In future versions of MongoDB a customer should only be able to enable secondary throttle by explicitly setting a write concern such as the example below.
|