[SERVER-57021] Release locks before DB refresh in rename coordinator Created: 18/May/21 Updated: 29/Oct/23 Resolved: 18/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1965-Milestone-1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2021-05-31 | ||||
| Participants: | |||||
| Linked BF Score: | 151 | ||||
| Description |
|
In case of rename between DBs, the database and collection locks are acquired on the source collection before performing a check on the database that is not allowed to happen if locks are held. The test statement supposedly ensuring that rename between DBs works on the DDL coordinator, needs to be updated because it is wrongly renaming test.unSharded to test.otherDBSamePrimary.unsharded. |
| Comments |
| Comment by Githook User [ 18/May/21 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |