[SERVER-77541] ReshardCollectionCoordinator must persist config time Created: 29/May/23 Updated: 29/Oct/23 Resolved: 20/Jun/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: | Pol Pinol | Assignee: | Pol Pinol |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26 |
| Participants: |
| Description |
|
The ReshardCollectionCoordinator must persist the config time after sending ConfigSvrReshardCollection. 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 [ 20/Jun/23 ] |
|
Author: {'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}Message: |