Simulate the Max Int reached into the LogicalClock error

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • 3.5.9
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • Sharding 2017-06-19, Sharding 2017-07-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

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

              Created:
              Updated:
              Resolved: