[SERVER-12539] Make sure mongorestoring user/role data doesn't interfere with ongoing user or role modifications Created: 29/Jan/14 Updated: 11/Jul/16 Resolved: 05/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security, Sharding, Tools |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If you use mongorestore to restore user or role data, those updates could conflict with other user or role management operations going on in the cluster. Proposed way to do this is to introduce two new commands: lockAuthzUpdateLock and unlockAuthzUpdateLock, and use them in mongorestore. |
| Comments |
| Comment by Githook User [ 05/Mar/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: This is done by making mongorestore insert the users/roles from the dump files into temporary |
| Comment by Githook User [ 29/Jan/14 ] |
|
Author: {u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}Message: There are some known caveats: (2) To restore 2.4 users to a 2.6 system that has never had any users added, you |