[SERVER-46859] Use namespace parameter with find fail point in router_transactions_metrics.js Created: 13/Mar/20  Updated: 29/Oct/23  Resolved: 13/Mar/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc0, 4.7.0

Type: Bug Priority: Major - P3
Reporter: Jack Mulrow Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: sharding-4.4-stabilization
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Problem/Incident
is caused by SERVER-46395 Resumable range deleter can submit du... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Sharding 2020-03-23
Participants:
Linked BF Score: 0

 Description   

router_transactions_metrics.js uses a fail point that hangs find commands to ensure a transaction is actively running when it checks transaction metrics in serverStatus. It uses currentOp to wait for exactly one thread to reach the fail point, but as of SERVER-46395, the range deleter runs a find that can trigger the fail point at the same time as the transaction, causing the test to hang. The fail point should instead use the "nss" parameter so only the transaction find will trigger the fail point.



 Comments   
Comment by Githook User [ 28/Mar/20 ]

Author:

{'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}

Message: SERVER-46859 Use namespace parameter with find fail point in router_transactions_metrics.js

(cherry picked from commit 69c511dcd726d4aba961df704981b62b9b297121)
Branch: v4.4
https://github.com/mongodb/mongo/commit/3b81a084c3bfbe8ecf2aeafa37cbf7cd3ffcead5

Comment by Githook User [ 13/Mar/20 ]

Author:

{'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-46859 Use namespace parameter with find fail point in router_transactions_metrics.js
Branch: master
https://github.com/mongodb/mongo/commit/69c511dcd726d4aba961df704981b62b9b297121

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