[SERVER-51892] Collection creation fails with NamespaceExists (code 48) after a collection drop in mongoshell in test suite sharded_causally_consistent_jscore_passthrough Created: 30/Oct/20  Updated: 30/Oct/20  Resolved: 30/Oct/20

Status: Closed
Project: Core Server
Component/s: Catalog, Testing Infrastructure
Affects Version/s: None
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Mindaugas Malinauskas Assignee: Max Hirschhorn
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Collection creation fails with NamespaceExists (code 48) after a preceding collection drop in mongoshell in test suite sharded_causally_consistent_jscore_passthrough. Failure happens only when additional options are passed to the create command.

Of cause, tests that issue a similar sequence could be excluded from the affected test suites, but it is not obvious why such code sequences should not be permitted in sharded_causally_consistent_jscore_passthrough test suite and others.



 Comments   
Comment by Max Hirschhorn [ 30/Oct/20 ]

mindaugas.malinauskas, the sharded_causally_consistent_jscore_passthrough.yml test suite uses the implicitly_shard_accessed_collections.js override to make the DBCollection.prototype.drop() function automatically re-created the namespace as a sharded collection. Running the create command immediately afterwards and getting a NamespaceExists error response is "Works as Designed" for this particular test suite.

You can use the "assumes_no_implicit_collection_creation_after_drop" tag to exclude the test from the sharded_causally_consistent_jscore_passthrough.yml test suite.

Generated at Thu Feb 08 05:26:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.