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

Use initClusterTimeFromTrustedSource when initializing LogicalClock

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Gone away
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-06-19

    Description

      Currently LogicalClock is initialized to 0 somewhere. Need to investigate how it happens and use initClusterTimeFromTrustedSource instead.

      2017-03-16T15:26:48.040-0400 E QUERY [thread1] Error: New cluster time, 0, is
      too far from this node's wall clock time, 1489692408. :
      connect@src/mongo/shell/mongo.js:237:13
      @(connect):1:6
      exception: connect failed

      Attachments

        Activity

          People

            misha.tyulenev@mongodb.com Misha Tyulenev
            misha.tyulenev@mongodb.com Misha Tyulenev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: