[SERVER-46098] Explore MaxTimeMS handling in thread local scope Created: 12/Feb/20  Updated: 29/Oct/23  Resolved: 14/Feb/20

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

Type: Bug Priority: Major - P3
Reporter: Eric Cox (Inactive) Assignee: James Wahlin
Resolution: Fixed Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2020-02-24
Participants:

 Description   

Replacing PooledScope with thread local scope doesn't allow for proper handling of .maxTimeMS() in a find query that contains a $where expression. This caused two test suites to fail that were subsquently blacklisted in SERVER-45454.

The work here should investigate how to correctly support MaxTimeMS in the js thread local scope machinery.

See SERVER-45454 for the relevant tests that were blacklisted.



 Comments   
Comment by Githook User [ 14/Feb/20 ]

Author:

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

Message: SERVER-46098 Register/deregister operation with JS Scope for every function invocation

With this change MaxTimeMS handling will work correctly for aggregation JavaScript
expressions. This change exposed a missing `catches_command_failures` tag exclusion
in a couple of the concurrency_sharded_multi_stmt_txn* suites and so adds them.
Branch: master
https://github.com/mongodb/mongo/commit/59745ff53a12a06ccdf73dd0f6eef3bdf118a902

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