[SERVER-37254] Retry on CursorNotFound in auto_retry_transaction.js when running the multi_statement_transaction_kill_sessions_atomicity_isolation workload Created: 21/Sep/18  Updated: 29/Oct/23  Resolved: 24/Sep/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.4

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-37009 Handle missing sessionDocToKill in sn... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-10-08
Participants:
Linked BF Score: 12

 Description   

In the multi_statement_transaction_kill_sessions_atomicity_isolation workload, we currently will retry on `CursorKilled` but not on `CursorNotFound` in auto_retry_transaction.js. We should also retry on this, however.



 Comments   
Comment by Githook User [ 24/Sep/18 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-37254 Retry on CursorNotFound error in multi_statement_transaction_kill_sessions_atomicity_isolation FSM workload
Branch: master
https://github.com/mongodb/mongo/commit/be8fffcd62e8af2e05597cad96941429a0990f4d

Generated at Thu Feb 08 04:45:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.