[SERVER-72957] stepdown suites logs are polluted with non relevant error messages Created: 17/Jan/23  Updated: 29/Oct/23  Resolved: 18/Jan/23

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

Type: Improvement Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-41096 ContinuousStepdown thread and resmoke... Closed
Related
is related to SERVER-48438 Include file name in open file assert... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-01-23
Participants:

 Description   

In all stepdowns suites logs are polluted with the following error message:

assert.soonNoExcept caught exception, exception: Error: couldn't open file /data/db/job0/resmoke/idle_ack

Usually around 10 times.

This is caused by this logic in the resmoke runner that waits for the stepdown thread to be ready. This is achieved by attempting to repeatedly open the idle_ack file, that will fail until the stepdown thread will be ready and will create it.

I believe all these error messages in the logs could be confusing and they do not really have much value since this error is expected.

 



 Comments   
Comment by Githook User [ 18/Jan/23 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-72957 Stepdown suites logs are polluted with non relevant error messages
Branch: master
https://github.com/mongodb/mongo/commit/e12c92b1673d9761c65139ac838213171d9e5cb6

Generated at Thu Feb 08 06:23:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.