[SERVER-49699] waitForCurOpByFailPoint shouldn't ignore filter parameter in 4.4 Created: 17/Jul/20  Updated: 29/Oct/23  Resolved: 05/Aug/20

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

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2020-08-10
Participants:
Linked BF Score: 37

 Description   

In master, the waitForCurOpByFailPoint() helper takes an optional filter argument and uses it to wait for a matching operation to hit a fail point. jstests/sharding/kill_pinned_cursor.js uses waitForCurOpByFailPoint() with a filter argument in 4.4 but in 4.4 the helper ignores the filter.



 Comments   
Comment by Githook User [ 05/Aug/20 ]

Author:

{'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}

Message: SERVER-49699 waitForCurOpByFailPoint shouldn't ignore filter parameter in 4.4
Branch: v4.4
https://github.com/mongodb/mongo/commit/c5864d0194ff8f1d2164eaa42180b832f94127db

Comment by Nicholas Zolnierz [ 23/Jul/20 ]

Nice catch jack.mulrow, I don't know what happened with the backport for SERVER-48502 but it looks like it just straight up missed the filter argument in the helper.

Comment by Jack Mulrow [ 17/Jul/20 ]

I assigned this to the query backlog because it looks like the use of a filter with waitForCurOpByFailPoint() was added to kill_pinned_cursor.js in SERVER-48502.

Generated at Thu Feb 08 05:20:34 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.