Details
-
Bug
-
Resolution: Won't Do
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/#secondary-throttle
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36
*Screen Resolution*: 1366 x 768
*repo*: docs
*source*: tutorial/configure-sharded-cluster-balancer
*Location*: https://docs.mongodb.org/manual/tutorial/configure-sharded-cluster-balancer/#secondary-throttle *User-Agent*: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36 *Screen Resolution*: 1366 x 768 *repo*: docs *source*: tutorial/configure-sharded-cluster-balancer
Description
Hi
I was directed to this Jira comment by the sharding devs:
https://jira.mongodb.org/browse/SERVER-14041?focusedCommentId=660934&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-660934
I think some of that info can be used to make the #secondary-throttle more clear. For example, please also cover the behavior for waitForDelete and how write concern affects that.