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

Investigate batched_multi_deletes.js failures with moveCollection

    • Catalog and Routing
    • v8.0
    • 0

      batched_multi_deletes.js fails if executed in sharding suites that performs random migrations (e.g. moveCollection) in background.

      Example of failed execution:

      WriteError({
          "index" : 0,
          "code" : 82,
          "errmsg" : "no progress was made executing batch write op in test.c after 5 rounds (0 ops completed in 6 rounds total)",
          "op" : {
              "q" : {
                  "_id" : {
                      "$gte" : 0
                  }
              },
              "limit" : 0
          }
      }) :
      WriteError({
          "index" : 0,
          "code" : 82,
          "errmsg" : "no progress was made executing batch write op in test.c after 5 rounds (0 ops completed in 6 rounds total)",
          "op" : {
              "q" : {
                  "_id" : {
                      "$gte" : 0
                  }
              },
              "limit" : 0
          }
      })
      WriteError@src/mongo/shell/bulk_api.js:465:48
      mergeBatchResults@src/mongo/shell/bulk_api.js:857:49
      executeBatch@src/mongo/shell/bulk_api.js:926:30
      Bulk/this.execute@src/mongo/shell/bulk_api.js:950:29
      DBCollection.prototype.deleteMany@src/mongo/shell/crud_api.js:432:22
      populateAndMassDelete@jstests/core/write/batched_multi_deletes.js:48:31
      @jstests/core/write/batched_multi_deletes.js:52:22
      failed to load: jstests/core/write/batched_multi_deletes.js
      

       

            Assignee:
            Unassigned Unassigned
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: