[SERVER-76463] Ensure Sharding DDL locks acquired outside a coordinator wait for DDL recovery Created: 24/Apr/23 Updated: 22/Nov/23 Resolved: 31/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 7.0.0-rc10, 6.0.10, 5.0.21 |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Silvia Surroca |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||||||
| Sprint: | Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 146 | ||||||||||||||||||||||||
| Description |
|
DDL locks acquired outside ShardingDDLCoordinator infrastructure does not properly synchronize with other DDL operations in case of failovers/stepdowns. Recovery of DDL locks for Sharding DDL coordinator works in the following way:
DDL locks acquired outside the ShardingDDLCoordinator infrastructure does not wait for the recovery of DDL locks acquired before the stepdown. We should ensure that DDL locks can be acquired only after all DDL locks acquired from the previous primary node have been recovered. |
| Comments |
| Comment by Gil Alon [ 26/Sep/23 ] |
|
Requesting a backport for this ticket, since |
| Comment by Githook User [ 30/May/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |