[DOCS-10911] Specify the roles/privileges required to resize the oplog Created: 18/Oct/17 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Linda Qin | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | docs-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
|
Currently the document Change the Size of the Oplog doesn't mention the roles/privileges required to resize the oplog. Before MongoDB 3.2.12, the admin user with readWriteAnyDatabase or dbAdminAnyDatabase roles have the privileges on the local database. So the admin user should not have any issue to execute the commands outlined in the document to resize the oplog. However, since 3.2.12, `*AnyDatabase` roles no longer provide access rights to the `config` or `local` databases ( |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |