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

Unify how we perform no-op writes

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Cluster Scalability

    Description

      We have a lot of similar code for performing a no-op write:

      On initial inspection it seems like almost all of these cases could be replaced with a call to resharding::doNoopWrite. I'm not sure what the distinction between onOpMessage and onInternalOpMessage is. Also, some of these callers wrap the operation in a DBLock which does not appear to be required in all cases.

      We should decide on a single helper for this, and reuse that helper where possible in the above linked locations.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated: