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

    • Fully Compatible
    • v4.4, v4.2
    • Sharding 2020-03-23
    • 18

      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.

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

              Created:
              Updated:
              Resolved: