[DOCS-4341] update/correct documentation for _secondaryThrottle Created: 11/Nov/14  Updated: 16/Mar/15  Resolved: 05/Dec/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.15

Type: Improvement Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-1189 update/correct documentation for _sec... Closed
is related to DOCS-4318 Document secondaryThrottle improvements Closed
Participants:
Days since reply: 9 years, 10 weeks, 5 days ago

 Description   

http://docs.mongodb.org/v2.4/tutorial/configure-sharded-cluster-balancer/#require-replication-before-chunk-migration-secondary-throttle

The title of the linked section is incorrect:
"Require Replication before Chunk Migration (Secondary Throttle)"

Regardless of the setting of _secondaryThrottle a chunkMove will wait for replication (if it is too far behind) before initiating migration. This behavior is hard-coded.

_secondaryThrottle only takes effect during chunk migration and refers to the commitment stage of the move (i.e whether or not the source documents are deleted from the originating shard before or after a secondary has confirmed replication).

Interestingly, the body text on that page is stated correctly, albeit somewhat subtly.

I think it is worth calling out this difference in wording. Explicitly stating that _secondaryThrottle only applies during a chunk migration and that the chunk move will not be started (regardless) until secondaries are within 10 hours (also hard-coded) of being up-to-date.



 Comments   
Comment by Githook User [ 05/Dec/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-4341: correction to secondaryThrottle
Branch: v2.4
https://github.com/mongodb/docs/commit/3b33ff53c82010590b28eb59629b867728eb4711

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