[SERVER-71918] DropCollectionCoordinator must persist config time Created: 07/Dec/22 Updated: 29/Oct/23 Resolved: 25/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | DDL-persist-vector-clock | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2023-05-15, Sharding EMEA 2023-05-29 | ||||||||
| Participants: | |||||||||
| Description |
|
The DropCollectionCoordinator must persist the config time after removing the collection entry and its associated chunks from config server. This will ensure that even in case of stepdown the next primary, during collection metadata refresh won't read stale information from the config server. |
| Comments |
| Comment by Githook User [ 25/May/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |