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

Re-enable validation checks that were disabled in SERVER-86451

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Execution Team 2024-04-01, Execution Team 2024-04-29, Execution Team 2024-06-10

      SERVER-86451 introduced a change in behavior where inconsistencies detected with time-series collections during validation would error instead of creating a warning. As a result of this, some tests that would previously pass with warnings were now failing. One of the changes in this ticket involved disabling this check and this check in testing. This ticket would look into the behavior causing the inconsistencies and re-enable the checks. Also, as part of this, some integration tests had validation disabled on shutdown - this ticket could look into re-enabling this test as well.

      For the check comparing the control.min timestamp and the observed min timestamp, after some discussion it appears that checking for strict equality is not enforceable when granularity is modified. Tentatively a bound on this would be control.min >= observed min timestamp - rounding seconds - this still caused the test to fail, so this ticket would build off of that.

            Assignee:
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Reporter:
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: