-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Environment:
*Location*: https://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/tutorial/manage-sharded-cluster-balancer/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: tutorial/configure-sharded-cluster-balancer
*Location*: https://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/ *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/tutorial/manage-sharded-cluster-balancer/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: tutorial/configure-sharded-cluster-balancer
secondaryThrottle setting explanation is not correct. There is no separate writeConcern field (this is only for internal commands). Also see https://jira.mongodb.org/browse/SERVER-14041?focusedCommentId=660934&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-660934
- duplicates
-
-
- Closed
-