[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:
Related
Participants:
Days since reply: 9 years, 31 weeks, 6 days ago

 Description   

http://docs.mongodb.org/manual/faq/concurrency/#does-a-mongodb-operation-ever-lock-more-than-one-database

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: DOCS-3491: edits to concurency about locking in authentication
Branch: master
https://github.com/mongodb/docs/commit/cc1a926ae3752a3a2bc84da098dad7cf69660539

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