[SERVER-48102] Update heartbeat state on primary even if heartbeat response includes a new config Created: 11/May/20 Updated: 29/Oct/23 Resolved: 13/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc7, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Siyuan Zhou | Assignee: | Siyuan Zhou |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | safe-reconfig-related | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||||||
| Sprint: | Repl 2020-05-18 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 37 | ||||||||||||||||||||||||
| Description |
|
When heartbeat response has a newer config, the node tries to install the config immediately without updating the heartbeat state. We should update the heartbeat state even if topology coordinator sees a newer config. It's less ideal to move the logic of |
| Comments |
| Comment by Githook User [ 14/May/20 ] |
|
Author: {'name': 'William Schultz', 'email': 'william.schultz@mongodb.com', 'username': 'will62794'}Message: (cherry picked from commit 2546fe1c22b0777ca68e604376900ea11f10ee3a)
(cherry picked from commit 74cc45677605baf25cd57caa497e254883e88567)
(cherry picked from commit 852d7eb6c7e7b34a78bd6f69ec8c1a65fa179c9e) |
| Comment by Githook User [ 13/May/20 ] |
|
Author: {'name': 'Siyuan Zhou', 'email': 'siyuan.zhou@mongodb.com', 'username': 'visualzhou'}Message: |