kCreate/kDrop/kTruncateRange oplog entries are not checked for replicated fast count eligibility

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • Storage Execution 2026-05-11, Storage Execution 2026-05-25
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When we process oplog entries (processOplogEntry), for basic CRUD operations we check whether the entries are on collections that are eligible to be tracked by the replicated fast count system (here). We do not perform this same check for kCreate, kDrop, or kTruncateRange oplog entries - we update fast count entries for these operations unconditionally

            Assignee:
            Damian Wasilewicz
            Reporter:
            Damian Wasilewicz
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: