Only attach a shared operation id to retry attempts when APM/logging is enabled

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      Describe the background behind the problem.
      PYTHON-5903 ensured that all retry attempts share a single operation id. However, it does so even if there is no active event listener or logger, causing a ~5-10% performance regression due to extra overhead on very fast operations such as pings.

      Definition of done

      What must be done to consider the task complete?
      A shared operation id should only be attached to retry attempts if APM or logging is enabled.

      Pitfalls

      What should the implementer watch out for? What are the risks?
      N/A.

            Assignee:
            Noah Stapp
            Reporter:
            Noah Stapp
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: