[SERVER-38294] WiredTiger oplog manager should include pretty-printed visibility timestamp in log message Created: 28/Nov/18  Updated: 29/Oct/23  Resolved: 06/Dec/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.7

Type: Improvement Priority: Minor - P4
Reporter: William Schultz (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-12-17
Participants:

 Description   

WiredTigerOplogManager::_setOplogReadTimestamp prints out the new oplog visibility read timestamp as a raw uint64_t. For logging purposes it would probably be more useful to include the structured Timestamp e.g.

setting new oplogReadTimestamp: Timestamp(1543426580, 1)

instead of

setting new oplogReadTimestamp: 6628965379207069697



 Comments   
Comment by Githook User [ 06/Dec/18 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-38294 WiredTiger oplog manager should include pretty-printed visibility timestamp in log message
Branch: master
https://github.com/mongodb/mongo/commit/ce305db495c4ff622ba70d5d4ab916a4734ec3e7

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