clustered_group_atomicity.js is flaky because the concurrent insert can run before the side writes table is set up

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2026-08-17
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      clustered_group_atomicity.js uses waitForIndexBuildToStart which does not guarantee that the side write table has been set up because collection scan hasn't started. We should use waitForIndexBuildToScanCollection so avoid the concurrent write being written in the window before the collection scan starts because the write ends up as part of the collection scan rather than as a side write. Wait for the scan to start ensures we generate the side write to test the smart grouping for clustered collections.

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

              Created:
              Updated:
              Resolved: