-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Fully Compatible
-
Repl 14 (05/13/16)
This ticket combines the work to evaluate the performance impact of reducing (or even dropping) the secondary throttle during chunk migration and the actual code changes to make no throttle default.
This affects both the inserts and deletes – it might be different issues wrt/write concern.
The easiest change we can make is to substitute the w:2 writes after each document with a single majority write at the end of each stage.
These changes may or may not be feasible for MMAP V1, but given that as of version 3.0 the collection locks are fair, it might be possible to reduce the throttling for MMAP V1 as well.
- is depended on by
-
SERVER-22562 Protocol Version 1 causes very very slow chunk migrations
- Closed
- is duplicated by
-
SERVER-23340 Turn off moveChunk secondaryThrottle by default
- Closed
- is related to
-
SERVER-22276 implement "j" flag in write concern apply to secondary as well as primary
- Closed
- related to
-
SERVER-22769 cleanupOrphaned has duplicated writeConcern
- Closed