[SERVER-28459] Simulate the Max Int reached into the LogicalClock error Created: 23/Mar/17  Updated: 06/Dec/17  Resolved: 16/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Jack Mulrow
Resolution: Done 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, Sharding 2017-07-10
Participants:

 Description   

Add fassert to LogicalTime::reserveTicks that checks if its try to set the max time.
Use LogicalTimeFIxture to set the clusterTime and validate that the "GameOver" failure happens.



 Comments   
Comment by Githook User [ 16/Jun/17 ]

Author:

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

Message: SERVER-28459 Prevent the max value from being reached in the logical clock
Branch: master
https://github.com/mongodb/mongo/commit/1dfd505d9fd3547a963fe748c34690c0d5c9add4

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