Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-77925

Client command fails due to internal txn being aborted by FCV upgrade/downgrade

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Cluster Scalability
    • Sharding NYC 2023-06-12, Sharding NYC 2023-06-26, Sharding NYC 2023-07-10, Sharding NYC 2023-07-24, Sharding NYC 2023-08-07, Sharding NYC 2023-08-21, Sharding NYC 2023-09-04, Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16
    • 5

      FCV upgrade/downgrade causes internal transactions to be aborted and user will see
      "errmsg" : "operation was interrupted"
      an example log can be found here: https://parsley.mongodb.com/resmoke/8b5e9ff2466914cea4c6d9ce15ca64c5/test/175820e297a94702427454ba46f338ab?bookmarks=0,158,702&shareLine=158 

      for src/mongo/db/modules/enterprise/jstests/fle2/update_arrayFilters.js

      user command was:

            edb.basic.insertOne({"_id": 2, "first": "mark", "grades": [98, 100, 102]});

      Reason is: 
      [j2:prim] | 2023-04-22T02:30:18.948+00:00 I TXN 5875900 [conn283] "Unable to abort internal transaction","attr":
      {
      reason: {
      code: 251,
      codeName: "NoSuchTransaction",
      errmsg: "Transaction with

      { txnNumber: 0 }

      has been aborted."
      },
      txnInfo: {
      ...

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            adi.zaimi@mongodb.com Adi Zaimi
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: