[SERVER-27814] Make timestamp logging format consistent Created: 25/Jan/17  Updated: 06/Dec/17  Resolved: 17/Nov/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.0-rc5

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Pavithra Vetriselvan
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-9102 Improve Format of OpTime (Timestamp) ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04
Participants:

 Description   

Some timestamps are printed like Timestamp(1485168714, 2), some are printed like
5885e03d:1 and some are printed like 2017-01-23T10:52:56.460+0000.The first and last are useful and the second is almost never useful. We should audit all places where we log timestamps and clean up how we print them. This occurs because there are essentially 4 separate ways to stringify timestamps.

This work may be taken care of by the lamport clock project.



 Comments   
Comment by Githook User [ 16/Nov/17 ]

Author:

{'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}

Message: SERVER-27814 Prints Timestamp consistently, changes toString(), and removes toStringLong()

(cherry picked from commit 3248ccbff8078af7351ee39dda30f77a158fe7a6)
Branch: v3.6
https://github.com/mongodb/mongo/commit/fcf3ce24838425eda2d9b2aeb21be5b272d3eb6b

Comment by Githook User [ 16/Nov/17 ]

Author:

{'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}

Message: SERVER-27814 Prints Timestamp consistently, changes toString(), and removes toStringLong()
Branch: master
https://github.com/mongodb/mongo/commit/3248ccbff8078af7351ee39dda30f77a158fe7a6

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