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

yield_with_drop.js FSM workload should permit upserts to fail with NoProgressMade

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Sharding 2020-03-23
    • Linked BF Score:
      18

      Description

      The upserts performed by the $config.data.create() function may fail with a NoProgressMade error response from mongos due to a shard returning a CannotImplicitlyCreateCollection error response after the collection has been dropped.

      const cmdRes = db.runCommand({
          update: collName,
          updates: [{
              q: {_id: i},
              u: {$set: {a: i, b: this.nDocs - i, c: i, d: this.nDocs - i, e: "foo"}},
              upsert: true
          }]
      });
      

      We should add ErrorCodes.NoProgressMade to the $config.data.kAllowedErrors list.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              max.hirschhorn Max Hirschhorn
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: