[SERVER-53841] Additional logging for oplog_rollover.js Created: 15/Jan/21  Updated: 29/Oct/23  Resolved: 16/Jan/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.4, 4.2.15

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

Issue Links:
Backports
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2
Sprint: Execution Team 2021-01-25
Participants:
Linked BF Score: 23

 Description   

There's a very infrequent race occurring in oplog_rollover.js that is hard to diagnose without additional logging. I believe the issue is related to failing to create a new oplog stone with try-locks causing the test to hang as oplog truncation will not run as expected.



 Comments   
Comment by Githook User [ 17/May/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-53841 Additional logging for oplog_rollover.js
Branch: v4.2
https://github.com/mongodb/mongo/commit/32e142329ce15c2e923dbe285f34d75d9285e771

Comment by Githook User [ 16/Jan/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-53841 Additional logging for oplog_rollover.js

(cherry picked from commit b2b72dfa42b0a04d355d56088d4e0228447b0d3d)
Branch: v4.4
https://github.com/mongodb/mongo/commit/464c15b2ed2545e75112eac5882ec2c19cfbf81c

Comment by Githook User [ 16/Jan/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-53841 Additional logging for oplog_rollover.js
Branch: master
https://github.com/mongodb/mongo/commit/b2b72dfa42b0a04d355d56088d4e0228447b0d3d

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