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

load clusterId into memory on config server transition to primary if needed

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.10
    • Fix Version/s: 3.3.10
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Sharding 17 (07/15/16)
    • Linked BF Score:
      0

      Description

      The clusterId must be in memory before inserts to config.shards (from a 3.2 mongos) can be issued, since we should not do any network operations in the OpObserver for that insert.

        Attachments

          Activity

            People

            Assignee:
            esha.maharishi Esha Maharishi
            Reporter:
            esha.maharishi Esha Maharishi
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: