[SERVER-58546] Add log message to applyOps to preview which oplog entries will be applied Created: 14/Jul/21  Updated: 29/Oct/23  Resolved: 14/Jul/21

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 5.0.1, 5.1.0-rc0

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:
v5.0
Sprint: Execution Team 2021-07-26
Participants:

 Description   

In the event that the applyOps command fails, it would be helpful to know what it was trying to apply to make investigations easier into the problem.

For example, mongomirror batches together oplog entries into single applyOps commands but it has no option to log the ops that are being applied.

 

The message would need to have a higher log level to avoid spam.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 15/Jul/21 ]

Author:

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

Message: SERVER-58546 Add log message to applyOps to preview which oplog entries will be applied

(cherry picked from commit de682083aad8d3b39a35132883481b89b8c52df2)
Branch: v5.0
https://github.com/mongodb/mongo/commit/318fd9cabc59dc9651f3189b622af6e06ab6cd33

Comment by Githook User [ 14/Jul/21 ]

Author:

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

Message: SERVER-58546 Add log message to applyOps to preview which oplog entries will be applied
Branch: master
https://github.com/mongodb/mongo/commit/de682083aad8d3b39a35132883481b89b8c52df2

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