Uploaded image for project: 'Compass '
  1. Compass
  2. COMPASS-7033

Investigate changes in SERVER-49202: Add serverStatus metric for interrupted operations due to disconnect.

    • Type: Icon: Investigation Investigation
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • No version
    • Affects Version/s: None
    • Component/s: None
    • None
    • Not Needed

      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)

            Assignee:
            rhys.howell@mongodb.com Rhys Howell
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: