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

Correct how _isTopologyChanged in sharded_backup_restore.js looks for removeShard oplog entries

    • Fully Compatible
    • ALL
    • 38

      The _isTopologyChanged() function checks for any oplog entries that are document deletions on config.shards. However, these oplog entries were changed by SERVER-47406 to become an applyOps (so that the topologyTime of some other shard can be updated, much like how chunk versions are updated). This means that this code no longer notices these removeShard events (even when they are supposed to happen), causing test failures. It needs to be updated to look for the "d" op nested inside an appropriate applyOps ops on config.shards (much like in the ConfigServerOpObserver). If these tests run in any multiversion suites then it should probably also retain the existing check for plain "d" ops on config.shards.

            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            kevin.pulo@mongodb.com Kevin Pulo
            0 Vote for this issue
            6 Start watching this issue