-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
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