[DOCS-12592] Restoring from Sharded Collection instructions fail with authentication Created: 02/Apr/19 Updated: 30/Oct/23 Resolved: 02/May/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Danny Hatcher (Inactive) | Assignee: | Ravind Kumar (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 4 years, 40 weeks, 6 days ago | ||||||||
| Story Points: | 1 | ||||||||
| Description |
DescriptionThe instructions for restoring a sharding cluster from an existing backup will error at step D-3 (removing minOpTimeRecovery document) if authentication is enabled for the process as normal users do not have the appropriate rights to delete from the admin.system.versions. The instructions should account for authentication. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}Message: |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}Message: |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'name': 'rk-mongo', 'email': 'ravind.kumar@mongodb.com'}Message: |
| Comment by Githook User [ 02/May/19 ] |
|
Author: {'email': 'ravind.kumar@mongodb.com', 'name': 'rk-mongo'}Message: |
| Comment by Ravind Kumar (Inactive) [ 02/May/19 ] |
|
Currently doing a final test build before merging this to master. Will backport through to 3.4. |
| Comment by Spencer Jackson [ 02/Apr/19 ] |
|
root doesn't have every privilege, it just has a large number of safe privileges for user collections. System collections that are not intended to be messed with tend to remain locked down. We've sometimes granted privileges to the restore role to make restoration easier, but generally only under duress. Is this a problem for 4.0/4.2, or just 3.6 which is the linked document? Will every sharded restore need to perform this operation? |