SERVER-137972ClosedDone

Operations are not killed on client disconnect when a TLS client sends close_notify before closing

*aggregate* opts into kill-on-disconnect ({*}handleMarkKillOnClientDisconnect{*}), and over plain TCP an aggregate whose client has disconnected is killed with *ClientDisconnect* within about a second. Over TLS, if the client closes cleanly (sends a `close_notify` alert, then closes the socket), the operation is never detected as disconnected and runs to completion. The Go driver always closes this way, because Go's *crypto/tls* sends *close_notify* on {*}Close(){*}. The likely cause is

Affected Versions
Versions known to exhibit this issue
8.3.117.0.45
Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.