-
Type:
Bug
-
Resolution: Gone away
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: 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
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
- related to
-
SERVER-49146 Enable s3 archiving of data files for backup tests in src/mongo/db/modules/enterprise/jstests/hot_backups
-
- Closed
-