-
Type:
Task
-
Resolution: Won't Do
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We already attempt to raise a warning if the application uses the same MongoClient before and after a fork. With session pooling this behavior becomes even more undefined (PYTHON-1660) because the parent and child may end up using the same server session at the same time. We should consider if we want completely restrict this usage by raising an error instead of a warning.
Such a change would be backwards breaking for apps that are written incorrectly however I think a hard error might be better than undefined behavior.
- is related to
-
PYTHON-1992 Running bulk insert raises TransactionTooOld, Cannot start transaction X on session Y because a newer transaction Z has already started.
-
- Closed
-
- related to
-
PYTHON-1672 Implement Connection Monitoring and Pooling spec
-
- Released
-
-
PYTHON-1660 Driver session pools must be cleared after forking
-
- Closed
-
-
-
- Closed
-