[SERVER-24083] auth should not hold mutexes while doing DB operations Created: 06/May/16 Updated: 01/Feb/18 Resolved: 06/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | Needs Triage |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
This may cause operations to be blocked on database and/or global locks, but not report this as time spent acquiring locks. In addition, this means that timeouts may not be honored. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 06/May/16 ] |
|
The AuthorizationManager doesn't hold mutexes while doing database operations. The CacheGuard makes it so there can only be one thread doing a database operation at a time in the AuthorizationManager, but no other operations will be blocked, except for those that would also be doing a database operation. |