Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13667

Investigate changes in SERVER-44650: New test mode for foreground validate that doesn't silently fix fastcounts

    XMLWordPrintable

    Details

    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Nov10 - Nov 17, ServerDocs2020: Nov17 - Nov 24, ServerDocs2020: Nov24 - Dec1, ServerDocs2020: Dec1 - Dec8

      Description

      Description

      Downstream Change Summary

      This adds an optional parameter to the validate command 'enforceFastCount'. When enabled with:

      {enforceFastCount: true}
      

      validation will fail if the fast count is not equal to the true record count. When disabled with:

      {enforceFastCount: false}
      

      or if not specified, behavior is the same as before (where validate corrects the fast count if it is incorrect). Note that currently, fast counts are known to be incorrect in certain circumstances such as unclean shutdown or active prepared transactions.

      Description of Linked Ticket

      It might be possible to add a new mode for validate that checks fastcount values against the actual record count, and when the values do not match, fail validation instead of fixing the fastcounts. This mode would be used by our test infrastructure in suites that do not undertake unclean shutdowns.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              andrew.feierabend Andrew Feierabend (Inactive)
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 21 weeks, 6 days ago
                Date of 1st Reply: