primary_driven_index_build_internal_idents.js checks that index build started on secondary without guaranteeing it started

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2025-09-15
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Since commit quorum is disabled on primary driven index builds, it is not guaranteed that all secondaries will have actually started the index build when we check for the "Index build: starting" log.

      We could use assert.soon to wait for the secondary to eventually start the index build.

            Assignee:
            Shin Yee Tan
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: