[SERVER-22769] cleanupOrphaned has duplicated writeConcern Created: 19/Feb/16  Updated: 25/Apr/16  Resolved: 21/Apr/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Judah Schvimer
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-20224 Commands which write should take a wr... Closed
is related to SERVER-22233 Reduce the secondary throttling durin... Closed
Sprint: Sharding 13 (04/22/16), Repl 14 (05/13/16)
Participants:

 Description   

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.


Generated at Thu Feb 08 04:01:22 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.