[SERVER-37203] Expose non blocking api for acquiring db/collection locks Created: 19/Sep/18 Updated: 16/Nov/18 Resolved: 16/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 4.1.3 |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Geert Bosch |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Storage NYC 2018-10-08, Storage NYC 2018-10-22, Storage NYC 2018-11-05, Storage NYC 2018-11-19 | ||||||||
| Participants: | |||||||||
| Comments |
| Comment by Geert Bosch [ 10/Oct/18 ] |
|
Rather than creating more complexity in the lock manager, can't you just create a thread to do the aborts on threads that are granted the lock while the specified locker has a pending MODE_X lock? Then you'd be able to take a regular MODE_X lock for the critical section. |