-
Type: Task
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding 13 (04/22/16), Repl 14 (05/13/16)
cleanupOrphaned currently takes a writeConcern and a secondaryThrottle parameter. Since we're now waiting for writeConcern in the central Command::run(), this command is already waiting for writeConcern at the end. This writeConcern value is not, however, modified by the secondaryThrottle parameter like it is in cleanupOrphaned. cleanupOrphaned, when initiated by a user, thus now waits for writeConcern an extra time at the end. If we remove throttling we should also clean up the secondaryThrottle and writeConcern code.
- is related to
-
SERVER-20224 Commands which write should take a write concern
- Closed
-
SERVER-22233 Reduce the secondary throttling during chunk migration
- Closed