[SERVER-28358] Use initClusterTimeFromTrustedSource when initializing LogicalClock Created: 16/Mar/17  Updated: 27/Oct/23  Resolved: 06/Jun/17

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

Type: Bug Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-06-19
Participants:

 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



 Comments   
Comment by Misha Tyulenev [ 06/Jun/17 ]

Gone - never happen again.

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