[DOCS-3491] Locks in user authentication requests in 2.6 Created: 28/May/14 Updated: 16/Mar/15 Resolved: 10/Jul/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Angshuman Bagchi (Inactive) | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 31 weeks, 6 days ago | ||||
| Description |
|
States that "User authentication locks the admin database as well as the database the user is accessing". However in 2.6 once completely, upgraded to the 2.6 user authorization model, authentication will only ever take a read lock on the admin db, in the worst case. It will never take locks on non-admin databases. Please clarify the FAQ page with respect to this. |
| Comments |
| Comment by Githook User [ 10/Jul/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |