[SERVER-62511] Race in dbcheck_no_history_on_secondary.js Created: 11/Jan/22  Updated: 29/Oct/23  Resolved: 24/Jan/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.3.0, 4.4.13, 5.0.7

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:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v5.0, v4.4
Sprint: Execution Team 2022-02-07
Participants:
Linked BF Score: 21

 Description   

The test uses an assert.soon with a find(), then follows-up with an query using a filter on severity: "error". This is unreliable because it's possible for the health log to contain data other than the error severity, so the assert.soon does not guarantee the error entry is present yet.



 Comments   
Comment by Githook User [ 01/Feb/22 ]

Author:

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

Message: SERVER-62511 Fix race in dbcheck_no_history_on_secondary.js

(cherry picked from commit 2f9bf168ae85dfd3a5bb9c15c5e534660562470c)
Branch: v4.4
https://github.com/mongodb/mongo/commit/537b62b26124d966cfe6ebba34e06b23e0ebac2b

Comment by Githook User [ 26/Jan/22 ]

Author:

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

Message: SERVER-62511 Fix race in dbcheck_no_history_on_secondary.js

(cherry picked from commit 2f9bf168ae85dfd3a5bb9c15c5e534660562470c)
Branch: v5.0
https://github.com/mongodb/mongo/commit/7c61a98ce1503e51a1b539fb285a2e4fadc58108

Comment by Githook User [ 24/Jan/22 ]

Author:

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

Message: SERVER-62511 Fix race in dbcheck_no_history_on_secondary.js
Branch: master
https://github.com/mongodb/mongo/commit/2f9bf168ae85dfd3a5bb9c15c5e534660562470c

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