[SERVER-64998] Running scan_checked_replset.js fails to create dbcheck artifacts when operating on internal system collections Created: 28/Mar/22 Updated: 25/Apr/22 Resolved: 25/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Edwin Zhou | Assignee: | Eric Sedor |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Case: | (copied to CRM) | ||||||||||||
| Description |
|
The server disallows any collection created with ".system." in its name. When scan_checked_replset.js operates on system collections, it attempts to create the collection with names such as "admin.dbcheck_backup.system.users.3" which violates the constraint. We can modify the prefix generated in the scan script to use a different character:
|
| Comments |
| Comment by Eric Sedor [ 08/Apr/22 ] |
|
repair_checked_documents.py reads the saveColl/backupColl collection names that scan_checked_replset.js persists in config.unhealthyRanges, and so is agnostic to this change in naming convention in scan_checked_replset.js |