The secondaryThrottle parameter is used during the bulk insert/remove operations of migrations, but is not used during commit - this is somewhat inconsistent if the secondaryThrottle write concern is stronger than the (necessary) majority-of-nodes-caught-up write concern used by the migration commit.
By enforcing both majority-of-nodes and the specified secondaryThrottle, we should be as safe as before but also allow users to provide stronger migration commit guarantees.
- is related to
-
SERVER-16548 Allow enforcement of additional custom write concern at pre-commit
-
- Closed
-
-
DOCS-4318 Document secondaryThrottle improvements
-
- Closed
-
-
SERVER-14041 enhance secondaryThrottle parameter
-
- Closed
-
-
-
- Closed
-