[SERVER-50534] --repair fails when views exist Created: 25/Aug/20 Updated: 29/Oct/23 Resolved: 26/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Daniel Gottlieb (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Sprint: | Sharding 2020-09-07 | ||||||||
| Participants: | |||||||||
| Description |
|
Running with --repair causes the storage engine to not instantiate record stores as part of startup. However the existence of a <db>.system.views collection will result in the initializing the view catalog. The view catalog is not aware of the repair mode and thus tries to iterate its record store which does not exist. |
| Comments |
| Comment by Githook User [ 26/Aug/20 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: |
| Comment by Daniel Gottlieb (Inactive) [ 25/Aug/20 ] |
|
louis.williams, I'll let you manage the backports you'd like to see for this ticket. |