[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: |
|
||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||
| 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. |