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

Don't attempt catalog swap on config servers

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.10
    • Component/s: Sharding
    • None
    • Sharding
    • ALL
    • Sharding 2016-11-21, Sharding 2016-12-12, Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06

      During SCCC to CSRS upgrade, it's possible for setShardVersion to be called on a config server, causing it to cache a SCCC config server connection string. Later, if another SSV call runs with a CSRS connection string, the config server will attempt to call grid.forwardingCatalogManager()->scheduleReplaceCatalogManagerIfNeeded(), which will segfault because there is no catalog manager installed on config servers.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: