[SERVER-34795] killSessions should kill transactions prior to killing cursors Created: 02/May/18  Updated: 29/Oct/23  Resolved: 08/May/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.7.9
Fix Version/s: 4.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: James Wahlin Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-34707 Write JS test for transactions on ses... Closed
Related
related to SERVER-34781 Abandoned cursor in a transaction can... Closed
related to SERVER-35217 killSessions command attempts to kill... Closed
is related to SERVER-34732 collection drop hangs in test of tran... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-05-07, Repl 2018-05-21
Participants:

 Description   

This will help prevent killSessions from blocking on locks held by a transaction it plans to kill.

A suggested ordering for session kill is:

  1. Kill transactions
  2. Kill operations
  3. Kill cursors


 Comments   
Comment by Githook User [ 08/May/18 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

Message: SERVER-34795 killSessions should kill transactions prior to killing cursors
Branch: master
https://github.com/mongodb/mongo/commit/13e636974a37588232ff33a422b94bbe77f351cc

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