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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.5.11
    • Fix Version/s: 3.6.3, 3.7.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Sharding 2017-09-11, Sharding 2017-10-02, Sharding 2017-10-23, Sharding 2017-11-13, Sharding 2017-12-04, Sharding 2017-12-18
    • Linked BF Score:
      0

      Description

      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).

        Attachments

          Activity

            People

            Assignee:
            jack.mulrow Jack Mulrow
            Reporter:
            jack.mulrow Jack Mulrow
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: