Details
-
Improvement
-
Resolution: Works as Designed
-
Major - P3
-
None
-
None
-
None
Description
ExclusiveConnectionPool's Clear() appears to simply abandons all existing connections without closing them.
If Clear becomes a blocking operation then we're going to need a ClearAsync version also.
Closing the connections in the background is dangerous because it creates a possible race conditions where connections are opened faster than they are closed leading to resource exhaustion.
Attachments
Issue Links
- related to
-
CSHARP-2231 Handshake changes for SDAM and Auth
-
- Closed
-