[SERVER-69399] Wait for primary after replica set restart in disable_resumable_range_deleter.js Created: 02/Sep/22 Updated: 29/Oct/23 Resolved: 05/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc2, 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| 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 | ||||||||
| Backport Requested: |
v6.1
|
||||||||
| Sprint: | Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 20 | ||||||||
| Description |
|
In disable_resumable_range_deleter.js, the replica sets are being restarted. In one place, we are restarting the replica set and then running a bulk insert that targets that replica set. On one replica set, we call getPrimary, which waits for a primary to be elected. But on the other, we just run the bulk insert. If the primary has not yet finished stepping up, this can cause the bulk insert to fail |
| Comments |
| Comment by Githook User [ 13/Sep/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: (cherry picked from commit ddc6e3f3d2ec0288310807141da94ba24d79fb2b) |
| Comment by Githook User [ 05/Sep/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |