[SERVER-54191] Avoid fasserting in a tenant migration if recipient primary calls startup on oplog buffer after it steps down Created: 01/Feb/21 Updated: 29/Oct/23 Resolved: 18/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Vishnu Kaushik |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | pm-1791_other_required | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Repl 2021-02-22 |
| Participants: |
| Description |
|
In a tenant migration, if we step down the recipient primary before it has started up the oplog buffer, it seems it will fassert and fail here. We should probably handle this case by returning an error status instead of fasserting. |
| Comments |
| Comment by Githook User [ 18/Feb/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |