[DOCS-3030] Update downgrade docs to include invalidateUserCache as last step of sharded authorization downgrade Created: 28/Mar/14 Updated: 02/Apr/14 Resolved: 31/Mar/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint-slipstream | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 9 years, 46 weeks, 2 days ago | ||||||||
| Description |
|
This page includes a procedure to downgrade the user data from the 2.6 model to the 2.4 model. In a sharded system, however, the mongos won't detect that that the authorization model version has changed until its user cache is refreshed, which happens periodically according to the user cache invalidation interval or via manually running the invalidateUserCache command. We need to include something about this at the end of the downgrade docs. |
| Comments |
| Comment by Githook User [ 31/Mar/14 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |