[SERVER-26636] Add more info in currentOp when moveChunk is in 'join' mode Created: 14/Oct/16  Updated: 06/Dec/22  Resolved: 27/Oct/16

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

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-26607 waitForMoveChunkStep test helper shou... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

For debuggability and to differentiate between moveChunk commands that are actually doing work from ones that are waiting for another moveChunk command to complete. One possible way to do this is to use CurOp::setMessage_inlock.



 Comments   
Comment by Andy Schwerin [ 27/Oct/16 ]

It's not great, but a clever user can figure out which operation is actually executing the move chunk by looking at the operation message in curop.

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