[SERVER-29111] Stabilize clusterTime in jstests Created: 08/May/17  Updated: 30/Oct/23  Resolved: 08/May/17

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2017-05-29
Participants:
Linked BF Score: 0

 Description   

In order to effectively test causal consistency, we should be able to ensure clusterTime won't advance outside of our control. Investigation of BF-5488 seems to have shown that the config server is constantly advancing clusterTime, and this should be investigated as part of this ticket.



 Comments   
Comment by Githook User [ 08/May/17 ]

Author:

{u'username': u'jsmulrow', u'name': u'Jack Mulrow', u'email': u'jack.mulrow@mongodb.com'}

Message: SERVER-29111 remove assertion in causal_consistency_shell_support.js
Branch: master
https://github.com/mongodb/mongo/commit/98b894b02685e9e02ef6e2b1ac3515d85c871439

Comment by Jack Mulrow [ 08/May/17 ]

After discussing offline, we're just going to remove the assertion that clusterTime doesn't change since there probably isn't a way to prevent the config servers from periodically doing writes that will advance clusterTime.

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