[SERVER-53124] Rollback test fixture can hang when transitioning to steady state operations if the tiebreaker node is too stale to sync from the primary Created: 30/Nov/20 Updated: 29/Oct/23 Resolved: 08/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Noma | Assignee: | A. Jesse Jiryu Davis |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2020-12-14 | ||||
| Participants: | |||||
| Linked BF Score: | 16 | ||||
| Description |
|
When transitioning to steady state operations, the rollback test fixture reconnects the tiebreaker node and awaits replication. However, it is possible that by this point the primary's oplog has advanced far enough along that the tiebreaker node is too stale to catch up. This causes the test fixture to hang awaiting replication which will never occur. |
| Comments |
| Comment by Githook User [ 08/Dec/20 ] |
|
Author: {'name': 'A. Jesse Jiryu Davis', 'email': 'jesse@mongodb.com', 'username': 'ajdavis'}Message: |