[SERVER-78509] Add storage stats to replicated slow op log entries Created: 28/Jun/23  Updated: 02/Jan/24  Resolved: 29/Nov/23

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

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: repl-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-16521 Investigate changes in SERVER-78509: ... Backlog
Related
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0, v4.4
Sprint: Repl 2023-07-24, Repl 2023-11-27, Repl 2023-12-11
Participants:

 Description   

The current implementation of replicated slow operation logging, found in oplog_applier_impl.cpp finishAndLogApply() only logs very basic information about the slow operation: the BSON of the oplog entry itself, its wall clock duration, and its size.

For normal (client-generated) slow query operation logging, we also include a number of fields that are relevant only to client-initiated queries, like the read preference and the number of bytes returned. Finally, we include a storage section that includes information on how many bytes were read and written.
It is this last section that can be very valuable. I undertook a recent slowness investigation that turned out to be insert operations to a collection with very large multi-key index entries, and this could have been diagnosed a lot faster if we had the storage information in the replication slow logs like we do for regular slow log entries.



 Comments   
Comment by Githook User [ 28/Nov/23 ]

Author:

{'name': 'Pavi Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com', 'username': 'pvselvan'}

Message: SERVER-78509 Add storage stats to replicated slow op log
Branch: master
https://github.com/mongodb/mongo/commit/1d14115e6076faf1aadc76f9723be5aedfc7e0b7

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