[SERVER-36940] Remove assertion that we find exactly one session in multi_statement_transaction_kill_sessions.js Created: 30/Aug/18  Updated: 29/Oct/23  Resolved: 10/Sep/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.1.3

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
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2018-09-24
Participants:
Linked BF Score: 41

 Description   

In this workload, we run listSessions but exclude our own session from the results. Thus, it is possible to not return a session and fail the assertion here. We should instead check if we've found a session, and if not simply do nothing.



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

Author:

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

Message: SERVER-36940 Remove assertion in multi_statement_transaction_kill_sessions_atomicity_isolation.js
Branch: master
https://github.com/mongodb/mongo/commit/6b9078df949eb8bdfd828f5a0d2b7ee5c5de5966

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