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

Bring back no timeout write concern for commands in resharding coordinator

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 7.1.0
    • None
    • Cluster Scalability
    • ALL
    • 2

    Description

      A refactor made the coordinator use the appendMajorityWriteConcern helper method to attach the write concern of some of the commands it sends to the participants. However, it also inadvertently changed some of the commands that originally had no timeout to something with one. This is because it changed some of the places where it originally used this constant to call appendMajorityWriteConcern, which uses a different constant with non-zero wtimeout value.

      Attachments

        Activity

          People

            backlog-server-cluster-scalability Backlog - Cluster Scalability
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: