[SERVER-35342] kill_cursors_in_transaction.js should check for pending drop using $currentOp Created: 01/Jun/18  Updated: 29/Oct/23  Resolved: 01/Jun/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.0.0-rc1
Fix Version/s: 4.0.0-rc2, 4.1.1

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

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Repl 2018-06-04, Repl 2018-06-18
Participants:
Linked BF Score: 15

 Description   

kill_cursors_in_transaction.js currently checks that a drop has a pending X database lock by running a find with maxTimeMS and checking that it times out. This can hang if the find is profiled, since profiling will wait for an IX database lock and does not respect maxTimeMS. Instead, we should check that the drop has a pending X database lock using a $currentOp aggregation, which does not take locks.



 Comments   
Comment by Githook User [ 01/Jun/18 ]

Author:

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

Message: SERVER-35342 kill_cursors_in_transaction.js should check for pending drop using currentOp

(cherry picked from commit 65bb6d69d6c2ce86d3766e62f74dd3dc841bed5e)
Branch: v4.0
https://github.com/mongodb/mongo/commit/4f02771dff42e427fbc363837dfa821cd3cb4b63

Comment by Githook User [ 01/Jun/18 ]

Author:

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

Message: SERVER-35342 kill_cursors_in_transaction.js should check for pending drop using currentOp
Branch: master
https://github.com/mongodb/mongo/commit/65bb6d69d6c2ce86d3766e62f74dd3dc841bed5e

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