[SERVER-77925] Client command fails due to internal txn being aborted by FCV upgrade/downgrade Created: 08/Jun/23  Updated: 12/Dec/23

Status: Open
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Adi Zaimi Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Cluster Scalability
Sprint: 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
Participants:

 Description   

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: {
...



 Comments   
Comment by Adi Zaimi [ 08/Jun/23 ]

This was already discussed in https://jira.mongodb.org/browse/SERVER-70131?focusedCommentId=4898024&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-4898024

but now this is client facing command failure.

Generated at Thu Feb 08 06:36:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.