Add updateMany to timseries upgrade/downgrade with CRUD FSM test

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2026-02-02
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The FSM was added in SERVER-117382. We decided to add this test case in a separate ticket because updateMany executed concurrently with timeseries upgrade/downgrade can trigger an invariant:

      [j0] 2026-01-26T16:37:20.006+00:00 F  ASSERT   23081 [conn60] Invariant failure {"expr":"findRecord(opCtx, ru, loc, &data)","msg":"Didn't find RecordId RecordId(646977982cb4f77856f3053f39) in record store f403f29f-0b10-489b-b7de-5c81fe630de5","location":"src/mongo/db/storage/record_store_base.cpp:75:75:virtual RecordData mongo::RecordStoreBase::dataFor(OperationContext *, RecoveryUnit &, const RecordId &) const"}
      

            Assignee:
            Tommaso Tocci
            Reporter:
            Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: