[SERVER-66868] Fail point must be enabled on new primary before step up in range_deletion_ordering_with_stepdown.js Created: 31/May/22 Updated: 29/Oct/23 Resolved: 02/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 6.0.0-rc7 |
| Fix Version/s: | 6.0.0-rc10, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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 | ||||||||
| Backport Requested: |
v6.0
|
||||||||
| Sprint: | Sharding EMEA 2022-06-13 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 13 | ||||||||
| Description |
|
In range_deletion_ordering_with_stepdown.js, the hangBeforeDoingDeletion failpoint is enabled after the new primary steps up. This can allow an extra batches to be deleted before the orphan count assertions can run. The failpoint needs to be enabled on the new primary before step up. |
| Comments |
| Comment by Githook User [ 10/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit 3165867be30e6a7414608ebad8984758c876fb72) |
| Comment by Githook User [ 02/Jun/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |