[DOCS-8883] Instructions on Active Indexing Operations does not work Created: 28/Sep/16 Updated: 19/Jul/17 Resolved: 19/Jul/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Roy Rim | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 30 weeks ago | ||||||||
| Description |
|
Recently when attempting to kill an index operation with a customer we could not get the instructions here to work: The instructions say to run the following command to get active index operations:
I had to change the op: "query" to op: "command" to get this to work. I am unsure about the second part of the $or and if that part still works. |
| Comments |
| Comment by Allison Reinheimer Moore [ 19/Jul/17 ] |
|
Being addressed in |
| Comment by David Storch [ 29/Sep/16 ] |
|
ravind.kumar, the docs do appear to be out of date. In recent versions of the server, the op field reported by db.currentOp() reflects the "logical op". We make a distinction between the "network op", which is the opcode associated with actual network message sent over the wire, and the "logical op", which reflects the semantics of the operation. If you use the OP_QUERY command protocol to issue a createIndexes command, the logical op is OP_COMMAND but the network op is OP_QUERY. A similar example would be a find command issued using the OP_COMMAND protocol. This would have a logical op of OP_QUERY but a network op of OP_COMMAND. Does that make sense? I'm not sure exactly what version this changed in, but I could track it down if that would be helpful. |
| Comment by Ravind Kumar (Inactive) [ 28/Sep/16 ] |
|
david.storch might this be because in mongo shell some operations are using command instead of query? or is that strictly for the wire protocol. |