Do not use egress hook to set traceCtx

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • ALL
    • ClusterScalability Oct13-Oct27, ClusterScalability Oct27-Nov10
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When testing setting traceCtx on commands from integration tests I ran into an issue with traceCtx being set on the command sent to mongos, mongos sends the command to mongod but we try to attach traceCtx again via the egress hook.

      There doesn't seem to be a clean way of checking if traceCtx exists, deleting it, setting a new one via the egress hooks so I'm opting to do this in the RemoteCommandRequest constructor as an alternative.

            Assignee:
            Brett Nawrocki
            Reporter:
            Ben Gawel
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: