Bring back no timeout write concern for commands in resharding coordinator

XMLWordPrintableJSON

    • Cluster Scalability
    • Fully Compatible
    • ALL
    • v8.0
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Abdul Qadeer
              Reporter:
              Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: