-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Internal Code
-
Fully Compatible
-
v4.2, v4.0, v3.6
-
Sharding 2019-10-07, Sharding 2019-10-21, Sharding 2019-11-04, Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-16
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When a cursor is cleaned up because of logical session killing (either logical session timeout, or a killSessions command), it currently cleans up silently. This is non-obvious for users (especially when using no timeout cursors and default sessions).
It would be a useful diagnostic if that cleanup triggered a log line explaining the reason for the kill
- is related to
-
SERVER-45385 Unblacklist sharding/kill_sessions.js after SERVER-43246 backports have reached last-stable
-
- Closed
-
- related to
-
-
- Closed
-