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

Remove ThreadName's dependence on ThreadContext (& vice versa apparently)

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2022-05-16, Service Arch 2022-05-30
    • 135

      ThreadName is a low-level diagnostic, not a db business object.
      For maximum generality, it should not have any idea what mongodb is.
      The idea that there's a "pre-init" for ThreadName, or that it depends on a MONGO_INITIALIZER for ThreadContext to get started is a bad fit that
      causes bugs: SERVER-58194, SERVER-63852.

      After working on ThreadName's API I don't see a reason for it to be connected to ThreadContext.

            Assignee:
            billy.donahue@mongodb.com Billy Donahue
            Reporter:
            billy.donahue@mongodb.com Billy Donahue
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: