[DRIVERS-578] Driver session pools must be cleared after forking Created: 11/Oct/18  Updated: 14/Oct/20  Resolved: 14/Oct/20

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

Type: Task Priority: Major - P3
Reporter: David Golden Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-2857 Provide a reset method to be called o... Closed
depends on CXX-1672 Driver session pools must be cleared ... Closed
depends on MOTOR-277 Driver session pools must be cleared ... Closed
depends on PHPC-1284 Driver session pools must be cleared ... Closed
depends on PYTHON-1660 Driver session pools must be cleared ... Closed
depends on RUBY-1524 Driver session pools must be cleared ... Closed
Driver Compliance:
Key Status/Resolution FixVersion
PERL-1012 Fixed 2.1.0
PYTHON-1660 Fixed 3.10
RUBY-1524 Fixed 2.14.0
CXX-1672 Fixed 3.5.0
PHPC-1284 Fixed 1.7.0
MOTOR-277 Won't Fix
CDRIVER-2857 Fixed 1.14.0

 Description   

When a driver forks, not only must it close its sockets on one side of the fork, it must also clear the session pool. It must do so without calling endSessions so as to not invalid the cache on the other side of the fork.

See the this commit for details.



 Comments   
Comment by Alexander Golin (Inactive) [ 14/Oct/20 ]

Confirmed with Rust and Swift that tickets are not needed.

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