-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Async, Query Operations
-
None
The asynchronous cursor implementation checks out a new connection from the pool in order to send a kill cursor message. But that's unnecessary, because in most cases it already has a connection checked out, either from the initial query or a subsequent get-more. In those cases, it should use the connection that's already available rather than check out a new one.