_shardsvrBeginMigrationBlockingOperation command can't call setAllowMigrations within the command thread

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • CAR Team 2026-05-11, CAR Team 2026-05-25
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, _shardsvrBeginMigrationBlockingOperation issues a _configsvrSetAllowMigrations command without an lsid, but SERVER-121209 will require an lsid for every _configsvrSetAllowMigrations call. Since _configsvrSetAllowMigrations is invoked on the user's command thread (call site → coordinator), once we start attaching an lsid the tassert 10090100 will be hit because the opCtx sessionId won't match the command lsid.

      Therefore, we need to start issuing _configsvrSetAllowMigrations from a thread other than the user's command thread.

            Assignee:
            Aitor Esteve Alvarado
            Reporter:
            Silvia Surroca
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: