Operational Defect Database
BugZero found this defect 493 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
MongoDB | 2231832
Remove sharding exceptions from invalidated_cursors FSM
Last update date:
3/13/2024
Affected products:
MongoDB Server
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Info
In SERVER-33700 we decided to skip dropping database or dropping collection when the invalidated_cursors.js FSM run on sharded clusters. The reason was that after doing those drops the test was failing to perform inserts with error "unable to target write op for collection ... caused by ... database not found". Originally we correlate this error to a bug affecting dropping collections/databases on sharded cluster SERVER-17397. Considering that this bug have been fixed in 5.0 we should now remove these exceptions in the test.
Top User Comments
JIRAUSER1259232 commented on Wed, 13 Sep 2023 06:50:58 +0000: Moving to backlog for now as dependent issue needs time to be solved. JIRAUSER1274254 commented on Fri, 28 Jul 2023 15:29:13 +0000: tommaso.tocci@mongodb.com it seems that the problem still exists. Can you please have a look and advise on the next steps? JIRAUSER1274254 commented on Thu, 27 Jul 2023 14:19:42 +0000: I removed the exceptions by essentially reverting the changes in invalidated_cursors.js and the tests are still failing.
Steps to Reproduce
