[SERVER-60319] Make initial_sync_aborts_two_phase_index_builds.js resilient to primary stepdowns Created: 29/Sep/21  Updated: 05/Nov/21  Resolved: 05/Nov/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Pavithra Vetriselvan Assignee: Pavithra Vetriselvan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
duplicates SERVER-49028 initial_sync_aborts_two_phase_index_b... Closed
Backport Requested:
v5.0, v4.4
Sprint: Execution Team 2021-10-18, Execution Team 2021-11-01, Execution Team 2021-11-15
Participants:

 Description   

We could introduce a new priority 0 secondary to prevent the primary from stepping down while the first secondary is restarted or we could call getPrimary() in the test before attempting to insert documents to ensure the primary has stepped back up.


Generated at Thu Feb 08 05:49:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.