[SERVER-60634] Bring backing the default catchup timeout Created: 12/Oct/21 Updated: 27/Oct/23 Resolved: 11/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Wenbin Zhu | Assignee: | Judah Schvimer |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Sometimes due to bugs or other issues the primary stepup can be stuck and catchup takeover does not work. The catchup takeover timeout is a more reliable way to bail out of this situation because it only relies on the stepping up node itself, but by default it is disabled due to the introduction of catchup takeover. Alternatively we can do PM-1039, but that is a larger effort than bring back the default catchup timeout. |