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

Cleanup `onConcurrentShardSince` in `sharded_backup_restore.js`

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Sharding EMEA 2022-12-26
    • 161

      The sharded_backup_restore.js test is simulating a restore of a sharded cluster, resetting the history when the chunks are moved on a new cluster:

                  assert.commandWorked(configDb.chunks.update(
                      {shard: sourceShardName}, {$set: {shard: destShardName, history: []}}));
      

      Since the field added under SERVER-71615 always need to be consistent with the first element of the history, the test needs to be changed in order to also clear up that field.

            Assignee:
            silvia.surroca@mongodb.com Silvia Surroca
            Reporter:
            pierlauro.sciarelli@mongodb.com Pierlauro Sciarelli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: