[SERVER-26733] Don't attempt catalog swap on config servers Created: 21/Oct/16 Updated: 06/Dec/22 Resolved: 21/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.2.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding 2016-11-21, Sharding 2016-12-12, Sharding 2017-01-02, Sharding 2017-02-13, Sharding 2017-03-06 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
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. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 21/Oct/16 ] |
|
The fix is to make sure we never call https://github.com/mongodb/mongo/blob/d8f51ce1da816ab66c97509791a5954cf899c0ec/src/mongo/db/s/set_shard_version_command.cpp#L373 if we are a config server. |