[DOCS-1266] _secondaryThrottle true on balancer in 2.4 ? Created: 19/Mar/13  Updated: 18/Apr/13  Resolved: 18/Apr/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: siddharth.singh@10gen.com Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 43 weeks, 6 days ago

 Description   

In 2.4, _secondaryThrottle option has been turned to true by default for the moveChunk command. Has the setting been turned on to true on the balancer as well ?

Release notes say : "By default, all insert and delete operations that occur as part of a chunk migration in a sharded cluster will have an increased write concern, to ensure that at least one secondary acknowledges each insert and deletion operation. This change slows the potential speed of a chunk migration, but increases reliability and ensures that a large number of chunk migrations cannot affect the availability of a sharded cluster."
which makes me believe that it has

http://docs.mongodb.org/manual/reference/command/moveChunk/#moveChunk
explicitly says that it has been turned on be default

The balancer portion (all the way at the bottom) here doesnt say anything:
http://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/#require-replication-before-chunk-migration-secondary-throttle



 Comments   
Comment by auto [ 18/Apr/13 ]

Author:

{u'date': u'2013-04-18T13:49:46Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1266 update _secondaryThrotle section
Branch: master
https://github.com/mongodb/docs/commit/34e797c5c685531a8eba8534657f57079ae3b660

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