[DOCS-5181] chunk migration with _secondaryThrottle uses w:2, not w:1 Created: 07/Apr/15  Updated: 08/Apr/15  Resolved: 08/Apr/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: mongodb-3.0

Type: Bug Priority: Minor - P4
Reporter: Daniel Coupal Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 8 years, 45 weeks ago

 Description   

In the following documentation:
http://docs.mongodb.org/manual/core/sharding-chunk-migration/#jumbo-chunks

we have:

By default, each document operation during chunk migration propagates to at least one secondary before the balancer proceeds with the next document, which is equivalent to a write concern of { w: 1 }. You can set the writeConcern option on the balancer configuration to set different write concern semantics.

I believe it should be { w:2 }.

This page seems to have it right: http://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/



 Comments   
Comment by Githook User [ 08/Apr/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-5181 secondary throttle write concern
Branch: master
https://github.com/mongodb/docs/commit/ea2f26346539686fe0a2a30d12e1897c0e7439b6

Generated at Thu Feb 08 07:49:47 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.