[DRIVERS-2094] Document pitfalls for test-related ops on various environments Created: 23/Apr/19  Updated: 31/Mar/22

Status: Backlog
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Spec Change Priority: Major - P3
Reporter: Matt Broadstone Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
Depends
Driver Changes: Needed

 Description   

Create a document in the specifications repo to discuss pitfalls and special requirements for test-related operations on various environments.


Original description: Before this Command Monitoring Tests we need to drop a database, and recreate a collection. Conversations with esha.maharishi have revealed that drivers must explicitly run flushRouterConfig against connected mongos when we drop databases. jeff.yemin suggests we run against a single mongos (modifying the URI that mongo orchestration provides us to only use a single address), but Esha points out that this just happens work because of an optimization in the mongos that dropDatabase is called on.



 Comments   
Comment by Jeremy Mikola [ 29/Apr/19 ]

Might also be good for this document to mention using w:majority when creating/dropping collections for transaction-related tests (see: manual).

Generated at Thu Feb 08 08:24:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.