-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Server
-
Labels:None
----------------------------
Original Description
Here in the documentation we have the following example:
use config db.settings.update( { "_id" : "balancer" }, { $set : { "_secondaryThrottle" : true , "writeConcern": { "w": "majority" } } }, { upsert : true } )
This is in fact incorrect - write concern, if set that way, will not take effect. The correct way to set it is:
use config db.settings.update( { "_id" : "balancer" }, { $set : { "_secondaryThrottle" : { "w": "majority" } } }, { upsert : true } )
So the resulting document would look like:
MongoDB Enterprise mongos> db.getSiblingDB("config").settings.findOne() { "_id" : "balancer", "stopped" : false, "mode" : "full", "_secondaryThrottle" : { "w" : "majority" } }
----------------------------
Description
Scope of changes (files that need work and how much)
Impact to other docs outside of this product
MVP (work and date?)
Resources (e.g. Scope Docs, Invision)
- is duplicated by
-
DOCS-7218 Comment on: "manual/tutorial/configure-sharded-cluster-balancer.txt"
- Closed
- related to
-
DOCS-11937 WriteConcern argument description is incorrect for the moveChunk command
- Closed