[SERVER-39631] Fix lagged_config_secondary test to not turn on failpoint until it's needed Created: 15/Feb/19 Updated: 29/Oct/23 Resolved: 25/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Saltz (Inactive) | Assignee: | Matthew Saltz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-04-08 | ||||
| Participants: | |||||
| Linked BF Score: | 13 | ||||
| Description |
|
We should move turning on the failpoint to make the secondary stop applying oplog entries until just before this line, otherwise the insert can target the delayed secondary and timeout. |
| Comments |
| Comment by Githook User [ 25/Mar/19 ] |
|
Author: {'name': 'Matthew Saltz', 'username': 'saltzm', 'email': 'matthew.saltz@mongodb.com'}Message: |