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

Refactor how shard version information is associated with each connection

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Currently there's a map in s/shard_version.cpp that associated each client connection with a shard version. Might be better to store that version in each thread's thread-local ClientBase object.

            Assignee:
            Unassigned Unassigned
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: