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

Error if resharding's oplog application sees an unexpected oplog entry

XMLWordPrintableJSON

    • Fully Compatible
    • Sharding 2020-12-28
    • 1

      Includes oplog entries for create collection, applyOps containing create collection, renameCollection (until renaming a sharded collection is supported), dropDatabase (which should always be preceded by drop for collection), emptycapped, and convertToCapped.

      • Update the config.localReshardingOperations.recipient document to have an error state.
      • Report to the config server that the resharding operation has been aborted.
      • Crash the mongod process when testing-mode is enabled to surface this issue more readily in Evergreen. To ensure that we're testing the error recovery codepath, we won't want to crash the mongod process. We'll instead want to ensure that the reshardCollection command never fails with the special error that was reported by the mongod process to the config server.

            Assignee:
            janna.golden@mongodb.com Janna Golden
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: