[SERVER-66721] Donor sends immediate heartbeats to recipient nodes after applying split config locally Created: 24/May/22 Updated: 29/Oct/23 Resolved: 26/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Matt Broadstone | Assignee: | Didier Nadeau |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Server Serverless 2022-05-30 |
| Participants: |
| Description |
|
A primary will schedule immediate heartbeats to its listed members after applying a config during a reconfig, in order for those nodes to learn of the new config sooner. During a shard split, the donor applies a split config which removes recipient nodes from its member list, and thus will not schedule heartbeats to these nodes. Update the reconfig logic to also schedule heartbeats to recipient nodes if a split config has been applied. |
| Comments |
| Comment by Githook User [ 26/May/22 ] |
|
Author: {'name': 'Didier Nadeau', 'email': 'didier.nadeau@mongodb.com', 'username': 'nadeaudi'}Message: |