[SERVER-30457] Cancel catchup takeover if primary caught up according to heartbeats Created: 01/Aug/17 Updated: 30/Oct/23 Resolved: 29/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Samyukta Lanka | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Requested: |
v3.6
|
||||
| Sprint: | Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04 | ||||
| Participants: | |||||
| Description |
|
Every time a node receives a heartbeat from the primary and it has a catchup takeover scheduled, it will check if the primary has caught up. If the primary caught up, then the node will cancel the catchup takeover. |
| Comments |
| Comment by Githook User [ 11/Dec/17 ] |
|
Author: {'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}Message: (cherry picked from commit fed696cf30596737df326aed790cae54d9b6f748) |
| Comment by Githook User [ 11/Dec/17 ] |
|
Author: {'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}Message: (cherry picked from commit 4174a84257760cae2ea9fdb26e8d3e65feadf253) |
| Comment by Githook User [ 30/Nov/17 ] |
|
Author: {'name': 'Daniel Gottlieb', 'username': 'dgottlieb', 'email': 'daniel.gottlieb@mongodb.com'}Message: |
| Comment by Githook User [ 29/Nov/17 ] |
|
Author: {'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}Message: |
| Comment by Siyuan Zhou [ 28/Nov/17 ] |
|
Actually, the node that has scheduled a catchup takeover can check if any write happened in the current term, implying the primary is caught up, by learning of the last applied optime from any node. |