-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: 9.1.0-rc0
-
Component/s: Concurrency
-
None
-
Catalog and Routing
-
Fully Compatible
-
ALL
-
CAR Team 2026-11-09
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Issue
renameCollection is not idempotent, so if it is retried after a failover (stepdown/kill/retry), the retry can fail with a NamespaceNotFound error. So rename tests must either:
- Be excluded from stepdown suites, or
- Gracefully accept the NamespaceNotFound.
Some of our tests in jstests/concurrency do not follow this pattern (rather are only incidentally excluded for other reasons), so when new suites are added they start failing.
Some failures have been recently uncovered by SERVER-125744 which added concurrency+replica set+stepdown suites.
Affected tests
rename_collection_dbname_chain.js - Not excluded + unconditionally assumes rename succeeds. rename_collection_dbname_droptarget.js - Not excluded + unconditionally assumes rename succeeds. rename_collection_dbname_droptarget_create_to.js - Not excluded + unconditionally assumes rename succeeds. rename_capped_collection_dbname_chain.js - Not excluded + unconditionally assumes rename succeeds. rename_capped_collection_dbname_droptarget.js - Not excluded + unconditionally assumes rename succeeds. rename_collection_update.js - Test tagged requires_non_retryable_commands, but the new suite doesn't exclude this tag. timeseries_collmod_index_translation_atomic.js - Test accepts NamespaceNotFound if (runningWithConfigStepdowns || runningWithShardStepdowns), but the new suite set runningWithStepdowns.
Proposed fix
Review the list of tests above and ensure they are either excluded from stepdown suites, or they tolerate a NamespaceNotFound error.