[SERVER-17413] Various improvements to stageDebug command Created: 27/Feb/15  Updated: 06/Dec/22

Status: Open
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: features we're not sure of

Type: Improvement Priority: Major - P3
Reporter: J Rassi Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-17403 logOp fassert during stagedebug delet... Closed
Assigned Teams:
Query Execution
Participants:

 Description   

The stageDebug command should:

  • be able to run on secondaries (unless a write operation is requested)
  • acquire the appropriate collection lock in IS/IX mode
  • run with a yielding PlanExecutor
  • support the "update" stage (and other stages that may be missing)
  • possibly not automatically add a FETCH stage on top of the user-requested stage tree

We should also audit jstests/core/stages_*.js to ensure they provide the coverage we're looking for, and verify that the FSM suite is indeed able to run them in parallel after the collection lock changes are made.

(Or, as an alternative to the above work, we could outright remove the stageDebug command and associated tests.)



 Comments   
Comment by J Rassi [ 27/Feb/15 ]

Ah, thanks for pointing that out to me; I hadn't seen it come in. Striking it from the description list.

Comment by David Storch [ 27/Feb/15 ]

As of 6769eca988fd, the stagedebug command runs with a yielding plan executor. This commit adds FSM tests for yielding which make use of the stagedebug mechanism.

Generated at Thu Feb 08 03:44:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.