[SERVER-41350] Upgrade to 3.6 fails on name conflict with config database Created: 28/May/19 Updated: 27/Oct/23 Resolved: 14/Oct/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Upgrade/Downgrade |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Mark Brinsmead | Assignee: | Mira Carey |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Sprint: | Sharding 2019-07-01 | ||||
| Participants: | |||||
| Case: | (copied to CRM) | ||||
| Description |
|
Presence of a user-defined database named config in a 3.4 replica set can result in the follow errors (followed by a BACKTRACE and instance failure) on upgrade to 3.6:
|
| Comments |
| Comment by Mira Carey [ 07/Jun/19 ] |
|
Unfortunately, I think there's nothing to do here. the config db became a reserved name in 3.6 for standalones and replica sets, and there aren't any options that would allow aliasing it to a new name. The only option available here is to "rename" the database, which isn't currently possible. I.e. the only option is to dump and restore that db to a new, non-conflicting name. |