[SERVER-77674] killOpsForStorageEngineChange always logs an uninitialized OperationId Created: 01/Jun/23  Updated: 29/Oct/23  Resolved: 14/Jun/23

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

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

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2023-06-12, Execution EMEA Team 2023-06-26
Participants:

 Description   

The intention was to log the opId of the operations which we wait for, but we are using an unitialized OperationId.

https://github.com/10gen/mongo/blob/0ef2c68f58ea20c2dde99e5ce3ea10b79e18453d/src/mongo/db/storage/storage_engine_change_context.cpp#L119



 Comments   
Comment by Githook User [ 13/Jun/23 ]

Author:

{'name': 'Yu Jin Kang Park', 'email': 'yujin.kang@mongodb.com', 'username': 'ykangpark'}

Message: SERVER-77674 fix opId logging in killOpsForStorageEngineChange
Branch: master
https://github.com/mongodb/mongo/commit/cb21d7aa2e7e6e6e5c4a431f1efd3ba9b682cb07

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