[COMPASS-7033] Investigate changes in SERVER-49202: Add serverStatus metric for interrupted operations due to disconnect. Created: 19/Jul/23  Updated: 24/Jul/23  Resolved: 24/Jul/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Rhys Howell
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-49202 Add serverStatus metric for interrupt... Closed
Documentation Changes: Not Needed

 Description   
Original Downstream Change Summary

This patch adds two new counters to the serverstatus document:

metrics.operation.unsendableCompletedResponses counts the number of operations that completed server-side, but where the produced response could not be sent to the client (i.e. due to a network error with the connection from that client).

metrics.operation.killedDueToClientDisconnect counts the number of operations that were killed before completion because the client that sent the operation disconnected.

Description of Linked Ticket

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 Rhys Howell [ 24/Jul/23 ]

No devtools changes needed. We don't use the metrics from serverStatus directly.

Comment by PM Bot [ 19/Jul/23 ]

Fix Version updated for upstream SERVER-49202:
7.1.0-rc0

Generated at Wed Feb 07 22:45:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.