[SERVER-71280] Add test coverage for currentOp with CQF queries Created: 11/Nov/22 Updated: 29/Oct/23 Resolved: 04/Oct/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Alyssa Clark | Assignee: | Hana Pearlman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Optimization
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | QO 2023-09-18, QO 2023-10-02, QO 2023-10-16 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Followup from https://github.com/10gen/mongo/pull/8635#discussion_r1018385740 `currentop_query.js` does not run/verify any CQF queries currently. This does not work out of the box for two reasons: 1) the current sharded test environment and test queries are not CQF eligible, and 2) even in a simple environment with CQF-eligible queries, the mechanism used to block running queries to allow them to be reported in a concurrent `currentOp` call (setting `internalQueryExecYieldIterations=1` and using the `setYieldAllLocksHang` failpoint) doesn't cause CQF queries to block. If this is expected to work with CQF, it'd be worth investigating why it does not.
|
| Comments |
| Comment by Githook User [ 04/Oct/23 ] |
|
Author: {'name': 'Hana Pearlman', 'email': 'hana.pearlman@mongodb.com', 'username': 'HanaPearlman'}Message: |
| Comment by Ana Meza [ 15/Nov/22 ] |
|
Adding this to PM-2518, since it depends on adding support of yielding to Bonsai |