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

Mongos should not blindly pass 'hasWriteConcernError=false' to getErrorLabels

    • Fully Compatible
    • Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11

      At the very least, if commitTransaction is sent to a recovery router, the recovery router could target a stale coordinator primary and get back NoSuchTransaction for coordinateCommitTransaction with a writeConcern error. The recovery router should not attach TransientTransactionError in this case, since the transaction may have committed.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: