-
Type: Task
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Task: Investigate if mongo-orchestration can upgrade from pymongo 3.5 to 3.11
mongo-orchestration is currently stuck using pymongo 3.5.1 due to various server bugs related to attaching implicit sessions to commands when starting sharded clusters. This is explained in: https://github.com/10gen/mongo-orchestration/issues/235
Opening in Jira to make it easier to track this work because this is blocking Versioned API spec testing.
- related to
-
SERVER-53334 Hitting unexpected invariant failure, causing server shutdown
- Closed
- links to