[SERVER-48401] CollectionShardingRuntime's state change mutex always refers to the empty string Created: 26/May/20 Updated: 29/Oct/23 Resolved: 27/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 4.4.0-rc6 |
| Fix Version/s: | 4.4.0-rc8, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| 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.4
|
||||
| Sprint: | Sharding 2020-06-01 | ||||
| Participants: | |||||
| Description |
|
The constructor of CollectionShardingRuntime moves the namespace variable, but then uses it to initialise the state change mutex. This means the state change mutex for all collections have the same identifier, which is bad at least for reporting purposes, but also potentially could lead to deadlocks (although it is not a problem currently). |
| Comments |
| Comment by Githook User [ 28/May/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit 764b77bfe24784e740527b167c0a21d22842af30) |
| Comment by Githook User [ 26/May/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |