Use container write path when primary-driven index builds write to the skipped records tracker

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2025-09-01, Storage Execution 2025-09-15, Storage Execution 2025-09-29
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Similarly to SERVER-109545, we'll need to make primary-driven index builds use the container write path for temporary record stores so that those writes get replicated.

            Assignee:
            Stephanie Eristoff
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: