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

RefineCollectionShardKey does not check for transaction write concern errors

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4
    • Sprint:
      Sharding 2020-09-07

      Description

      It checks for top level errors here but never checks for write concern errors. Thus the command can succeed and then roll back.

      Here is an example of checking for both types of errors.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-48527 Aborting in-progress transactions on step-up should clear session state before returning

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              jack.mulrow Jack Mulrow
              Reporter:
              judah.schvimer Judah Schvimer
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: