Use initClusterTimeFromTrustedSource when initializing LogicalClock

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-06-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            Misha Tyulenev (Inactive)
            Reporter:
            Misha Tyulenev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: