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

Fix a bug where a sharded backup/restore test loses a record

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Sharding NYC
    • Sharding 2020-07-13, Sharding 2020-06-29, Sharding 2020-07-27, Sharding 2020-08-10, Sharding 2020-08-24, Sharding 2022-02-21, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11
    • 18
    • 8

    Description

      The MongoDB test suite has seen a failure where a sharded backup restore test doesn't see the expected set of records at the end of the test. The test is being run with majority read concern off.

      The test case is:

      src/mongo/db/modules/enterprise/jstests/hot_backups/sharded_last_stable_pit_backup_restore_simple.js
      

      Stacktrace:

      assert@src/mongo/shell/assert.js:151:9
      _verifyDataIsCausallyConsistent@src/mongo/db/modules/enterprise/jstests/hot_backups/libs/sharded_backup_restore.js:159:13
      _checkDataConsistency@src/mongo/db/modules/enterprise/jstests/hot_backups/libs/sharded_backup_restore.js:217:27
      ShardedBackupRestoreTest/this.run@src/mongo/db/modules/enterprise/jstests/hot_backups/libs/sharded_backup_restore.js:960:9
      @src/mongo/db/modules/enterprise/jstests/hot_backups/sharded_last_stable_pit_backup_restore_simple.js:24:11
      @src/mongo/db/modules/enterprise/jstests/hot_backups/sharded_last_stable_pit_backup_restore_simple.js:10:2
      

      Logs:

      assert failed : Doc 100 is missing
      

      Attachments

        Activity

          People

            lamont.nelson@mongodb.com Lamont Nelson
            alexander.gorrod@mongodb.com Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: