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

Investigate changes in SERVER-48578: Skip fast count enforcement on the oplog when running validate with enforceFastCount=true

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: 4.7.0
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Downstream Change Summary

      SERVER-44650 added the enforceFastCount mode to the validate command (documented by DOCS-13667). This ticket makes it so that the fast count will not be enforced when validate is run on the oplog collection, even if enforceFastCount is set to true (in other words, the enforceFastCount flag is ignored when validate is run on local.oplog.rs).

      Description of Linked Ticket

      Oplog writers only take a global IX lock, so the oplog can still be written to even during full validation despite its collection X lock. This can cause validate to incorrectly report an incorrect fast count on the oplog when run in enforceFastCount mode. Thus, even if enforceFastCount is specified, the fast count should not be enforced on the oplog.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                9 weeks, 4 days ago
                Date of 1st Reply: