[SERVER-77266] createCollection command in rename_capped_collection_droptarget.js should ignore "cannot find ns" errors Created: 18/May/23  Updated: 29/Oct/23  Resolved: 26/Jun/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.19, 6.0.8

Type: Bug Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Antonio Fuschetto
Resolution: Fixed Votes: 0
Labels: shardingemea-qw
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Backport Requested:
v6.0, v5.0
Sprint: Sharding EMEA 2023-06-26
Participants:
Linked BF Score: 11
Story Points: 1

 Description   

Due to SERVER-60933, this fsm workload may encounter "cannot find ns" errors. This behavior was fixed in 7.0 as a part of SERVER-60064, but we cannot backport a fundamental behavioral change to stable release versions.

In order to fix the test on 6.0 and 5.0, we should ignore these errors since it's possible for the collection to have been dropped before the call to listCollections (issued during the createCollection command).



 Comments   
Comment by Githook User [ 26/Jun/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-77266 Ignore `NamespaceNotFound` error in `rename_capped_collection_droptarget.js`
Branch: v5.0
https://github.com/mongodb/mongo/commit/85f22a6df3d86860d0c992b4016b3d5f8eb6b21a

Comment by Githook User [ 26/Jun/23 ]

Author:

{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}

Message: SERVER-77266 Ignore `NamespaceNotFound` error in `rename_capped_collection_droptarget.js`
Branch: v6.0
https://github.com/mongodb/mongo/commit/a7e9cc8d7812a995e0b1b5fdd87c0031709b267c

Comment by Antonio Fuschetto [ 20/Jun/23 ]

pavithra.vetriselvan@mongodb.com, since we already have a clean and working solution on 7.0 branch, I suggest implementing the suggested workaround on 6.0 branch and then backporting it to 5.0.

Generated at Thu Feb 08 06:35:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.