Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-22769

cleanupOrphaned has duplicated writeConcern

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 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.

            Assignee:
            judah.schvimer@mongodb.com Judah Schvimer
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: