-
Type: Bug
-
Resolution: Won't Fix
-
Priority: 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
-
(copied to CRM)
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.
- related to
-
SERVER-23428 If mongos tells a shard about a CSRS config server string (via SSV), the shard should switch to CSRS mode
- Closed