-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Fully Compatible
-
ALL
-
Storage Execution 2026-11-09
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
magic_restore_oplog_application.js uses truncateRange on a clustered collection with no secondary indexes:
// To test truncateRange, we create a clustered collection 'test.truncateColl' with 10 documents. // truncateRange only works on clustered collections with no secondary indexes. const truncateColl = "truncateColl"; assert.commandWorked( testDB.createCollection(truncateColl, {clusteredIndex: {key: {_id: 1}, unique: true}}), ); let docsBeforeTruncate = []; for (let i = 0; i < 10; i++) { docsBeforeTruncate.push({_id: i}); } assert.commandWorked(testDB[truncateColl].insertMany(docsBeforeTruncate));
Collection validation at the end of the test occasionally fails after SERVER-138410 because the size/count change from the truncate operation is not accounted for. See patch 1 and 2 for failures.
Fix the test, either by disabling shutdown validation or by supporting truncateRange operations on user collections.