[SERVER-34130] Log oplog truncation operation Created: 26/Mar/18  Updated: 29/Oct/23  Resolved: 06/Jun/18

Status: Closed
Project: Core Server
Component/s: Logging, Replication
Affects Version/s: None
Fix Version/s: 4.0.0-rc5, 4.1.1

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Audrey Fang (Inactive)
Resolution: Fixed Votes: 1
Labels: neweng, nyc, supportgrab2018Q2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Storage NYC 2018-06-04, Storage NYC 2018-06-18
Participants:
Case:

 Description   

Some users are sensitive to the short stalls that can be caused by oplog truncation, which can be a moderately heavy operation. This can be difficult to diagnose; we could make it easier to diagnose by logging each oplog truncation like we log normal operations. Since oplog truncations are infrequent events this could be logged without regard to the slowms threshold.



 Comments   
Comment by Githook User [ 08/Jun/18 ]

Author:

{'username': 'audreyfang', 'name': 'Audrey Fang', 'email': 'audrey.fang@10gen.com'}

Message: SERVER-34130 Log oplog truncation operation

(cherry picked from commit 62378f4e12644c250ccb894cf6b92d27b77b16fd)
Branch: v4.0
https://github.com/mongodb/mongo/commit/9983c17b0da32d0b0918c47e081840d3a9ac3a85

Comment by Githook User [ 06/Jun/18 ]

Author:

{'username': 'audreyfang', 'name': 'Audrey Fang', 'email': 'audrey.fang@10gen.com'}

Message: SERVER-34130 Log oplog truncation operation
Branch: master
https://github.com/mongodb/mongo/commit/62378f4e12644c250ccb894cf6b92d27b77b16fd

Comment by Bruce Lucas (Inactive) [ 26/Apr/18 ]

I think it would be helpful if it were logged after, and included the time taken. It would be good if it matched slow operation logging to whatever extent is reasonable; in particular, if the line ends with "<number>ms" then tools that look for that pattern will pick it up.

Comment by Michael Cahill (Inactive) [ 26/Apr/18 ]

bruce.lucas, for clarity, would you like logging before or after the truncate, or both?

Is it important that the output match the format of the log line for a slow operation?

Generated at Thu Feb 08 04:35:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.