[SERVER-30733] Make DistLocks hierarchical for mongos commands Created: 18/Aug/17 Updated: 30/Oct/23 Resolved: 12/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.11 |
| Fix Version/s: | 3.6.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Hugh Han | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding 2017-09-11, Sharding 2017-10-23 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, commands such as dropCollection take a lock for the collection it operates on, but not the database it operates on. Hence, commands that take a lock for only the database may be able to operate concurrently with dropCollection, which is not desired. Hierarchical distributed locks should be added to all instances that such issues may occur. |
| Comments |
| Comment by Githook User [ 12/Oct/17 ] |
|
Author: {'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}Message: |