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

Create ThreadClients with Service, not ServiceContext

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Service Arch 2023-10-16

      As part of ensuring all internal clients and operations are cluster-role-aware, they can be tagged with the Service (corresponding to a ClusterRole) they are running under. In this ticket, migrate ThreadClients that are being created with a raw ServiceContext to being created via a Service that they are a member of.

      For now, just use the "default service" on the ServiceContext, which will be either Router or Shard depending on the binary. After this ticket, we will need to tag them specifically as the use of a "default service" is eliminated.

            Assignee:
            george.wangensteen@mongodb.com George Wangensteen
            Reporter:
            george.wangensteen@mongodb.com George Wangensteen
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: