Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-86792

Report mongos host and port in client metadata sent by AsyncClient

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Diagnostics
    • Labels:
      None
    • Service Arch
    • Service Arch Prioritized List

      One of the challenges in diagnosing HELP-51094 / HELP-51359 was the inability to identify from the mongod logs which mongos had been used to send the command that ultimately crashed the mongod. This is because the mongod logs for the offending connection (thread) would only contain a "client metadata" log message followed later by a "BACKTRACE" log message with no other messages in between. Adding the mongos host and port to the context logged by the "client metadata" message would have made it simpler to look specifically at that particular mongos logs and FTDC for more clues.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: