[SERVER-45536] index_secondary_commit_after_scan_error.js should wait for the secondary before shutting it down Created: 13/Jan/20  Updated: 29/Oct/23  Resolved: 03/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-02-10
Participants:
Linked BF Score: 145

 Description   

The test waits for the primary to finish the index build, before immediately shutting down the secondary. If the secondary hasn't yet processed the "commitIndexBuild" oplog entry to prompts an fassert, then the node will exit cleanly. The test expects the node to crash.

Modify the test so that it does not try to shut down the secondary until it has processed the "commitIndexBuild" oplog entry.  IndexBuildTest.waitForIndexBuildToStop(secondaryDB) should be enough to fix the test.



 Comments   
Comment by Githook User [ 03/Feb/20 ]

Author:

{'name': 'Louis Williams', 'username': 'louiswilliams', 'email': 'louis.williams@mongodb.com'}

Message: SERVER-45536 index_secondary_commit_after_scan_error.js should wait for the secondary before shutting it down
Branch: master
https://github.com/mongodb/mongo/commit/6be973434ba90a6442c2e5ffecb04b75d08ab5b2

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