[DOCS-6253] Describe authz exception for mongorestore with oplogReplay Created: 22/Sep/15  Updated: 05/Oct/15  Resolved: 05/Oct/15

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: mongodb-2.6, mongodb-3.0

Type: Task Priority: Major - P3
Reporter: Andreas Nilsson Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-19191 "restore" role does not have applyOps... Closed
Participants:
Days since reply: 8 years, 19 weeks, 2 days ago

 Description   

As described in SERVER-19191 there is a bug in on the server that makes it impossible to do a mongodump/restore with --oplogReplay with the restore role. It is hard to fix so we are punting for 3.2.

We should document the following workaround in the mongorestore docs.

The only way to do a mongorestor with --oplogReplay on a system with access control enabled is to grant the __system role to the user restoring the data.



 Comments   
Comment by Githook User [ 05/Oct/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-6253 restore role is insufficient for mongorestore with oplogReplay
Branch: master
https://github.com/mongodb/docs/commit/4d10b39f7cadc7c47957bf7149dfa1d7cadc5308

Comment by Githook User [ 05/Oct/15 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-6253 restore role is insufficient for mongorestore with oplogReplay
Branch: v2.6
https://github.com/mongodb/docs/commit/604e42f2f7967e28245bdf8762dd693cd0b172d0

Generated at Thu Feb 08 07:51:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.