[SERVER-54172] verify_index_stats_output.js must wait for the failpoint to be hit rather than the index build to begin Created: 01/Feb/21  Updated: 29/Oct/23  Resolved: 12/Feb/21

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Nikita Lapkov (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 9

 Description   

The test verify_index_stats_output.js uses waitForIndexBuildToStart expecting it to mean that the failpoint previously set has been hit. However, that is not what waitForIndexBuildToStart does: it simply looks for a currentOp reported operation to be an index build.

I believe verify_index_stats_output.js has been passing (until now) by good fortune of a race. It needs to wait for the failpoint to be hit, for which we have JS test utilities, before expecting to find results in $indexStats.



 Comments   
Comment by Githook User [ 12/Feb/21 ]

Author:

{'name': 'Nikita Lapkov', 'email': 'nikita.lapkov@mongodb.com', 'username': 'laplab'}

Message: SERVER-54172 SERVER-54181 Make verify_index_stats_output.js wait for hangAfterStartingIndexBuild failpoint to be hit and disable secondary reads
Branch: master
https://github.com/mongodb/mongo/commit/ee8c15294b11a098ebcb766fd216b7f6986106a4

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