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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.3.10
    • Affects Version/s: 3.3.10
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 17 (07/15/16)
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Esha Maharishi (Inactive)
              Reporter:
              Esha Maharishi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: