[SERVER-49202] Add serverStatus metric for interrupted operations due to disconnect. Created: 30/Jun/20  Updated: 29/Oct/23  Resolved: 19/Jul/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.4.0-rc11
Fix Version/s: 7.1.0-rc0

Type: Improvement Priority: Minor - P4
Reporter: Kevin Arhelger Assignee: George Wangensteen
Resolution: Fixed Votes: 0
Labels: re-triaged-ticket, servicearch-metrics
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by COMPASS-7033 Investigate changes in SERVER-49202: ... Closed
Documented
is documented by DOCS-16276 Investigate changes in SERVER-49202: ... Closed
Related
is related to SERVER-49201 Add serverStatus metric for operation... Closed
Assigned Teams:
Service Arch
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0, v4.4
Sprint: Service Arch 2023-07-10, Service Arch 2023-07-24
Participants:

 Description   

Similar to SERVER-49201, I am not aware of a strong serverStatus indicator that a socket timeout was encountered in an application. i.e. “operation was interrupted because a client disconnected.” (SERVER-39150)

A count of operations that were halted due to disconnect, or couldn’t return data due to the client closing the socket in 4.0 may be diagnostically useful to determine application behavior.

 

(fixed typo for SERVER-49201)



 Comments   
Comment by George Wangensteen [ 19/Jul/23 ]

Done in https://github.com/mongodb/mongo/commit/7bbaf37d6ec596edfcc7a84f29cb23c2dbc4d341 Not sure what's up with the githook

Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:19:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.