-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Today
Currently customer can enable a secondary throttle in two different ways.
1. The customer can set secondary throttle to true in config.settings
use config
db.settings.updateOne(
{ "_id" : "balancer" },
{ $set : { "_secondaryThrottle" : true } },
{ upsert : true }
)
2. The customer can set secondary throttle with a explicit write concern in config.settings
use config
db.settings.updateOne(
{ "_id" : "balancer" },
{ $set : { "_secondaryThrottle" : { "w": "majority" } } },
{ upsert : true }
)
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.
use config
db.settings.updateOne(
{ "_id" : "balancer" },
{ $set : { "_secondaryThrottle" : { "w": "majority" } } },
{ upsert : true }
)