[SERVER-36433] NamespaceSerializer lock should be used during drop database Created: 03/Aug/18 Updated: 29/Oct/23 Resolved: 03/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.3, 4.1.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Janna Golden | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||
| Sprint: | Sharding 2018-08-13 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
We use the NamespaceSerializer lock to prevent distlock timeouts during create database and collection. We should also do this during drop database. |
| Comments |
| Comment by Githook User [ 28/Aug/18 ] |
|
Author: {'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}Message: (cherry picked from commit 5b1425734732ef5d8d906fe6cb18d9667df045ed) |
| Comment by Githook User [ 03/Aug/18 ] |
|
Author: {'username': 'jannaerin', 'name': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: |