[DOCS-16276] Investigate changes in SERVER-49202: Add serverStatus metric for interrupted operations due to disconnect. Created: 19/Jul/23 Updated: 13/Nov/23 Resolved: 03/Aug/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | David Hou |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 27 weeks, 1 day ago | ||||||||
| Story Points: | 2 | ||||||||
| 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 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 |
| Comments |
| Comment by David Hou [ 01/Aug/23 ] |
|
george.wangensteen@mongodb.com Requesting your review on this when you get a chance - thanks! |