Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-30671

Don't expect operationTime to not change in causal_consistency_shell_support.js

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.3, 3.7.1
    • Affects Version/s: 3.5.11
    • Component/s: Sharding
    • Labels:
    • Fully Compatible
    • ALL
    • v3.6
    • Sharding 2017-09-11, Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2017-12-18
    • 0

      Internal activity in the config server can lead to writes that advance operationTime, which can cause causal_consistency_shell_support.js to fail when it asserts that read commands don't advance operationTime. This check should be removed since there is no way to either prevent or ignore these writes.

      This is the same base problem as SERVER-29111, but is triggered less frequently, only failing in suites with either more CSRS activity or that run more slowly (I've seen failues in sharding-auth and the continuous stepdown suite).

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            0 Vote for this issue
            2 Start watching this issue