Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27814

Make timestamp logging format consistent

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc5
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Fully Compatible
    • v3.6
    • Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04

      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.

            Assignee:
            pavithra.vetriselvan@mongodb.com Pavithra Vetriselvan
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: