[SERVER-21769] Find, getMore, and killCursors command log lines should be in the QUERY log component Created: 04/Dec/15  Updated: 08/Jan/16  Resolved: 08/Jan/16

Status: Closed
Project: Core Server
Component/s: Logging, Querying
Affects Version/s: 3.2.0-rc6
Fix Version/s: None

Type: Bug Priority: Trivial - P5
Reporter: David Storch Assignee: J Rassi
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-21776 Move per-operation log lines for quer... Closed
Operating System: ALL
Sprint: QuInt E (01/11/16)
Participants:

 Description   

Currently, they are in the COMMAND log component:

2015-12-04T10:47:11.959-0500 I COMMAND  [conn1] command test.c command: find { find: "c", filter: {}, batchSize: 2.0 } planSummary: COLLSCAN cursorid:18886010290 keysExamined:0 docsExamined:2 keyUpdates:0 writeConflicts:0 numYields:0 nreturned:2 reslen:139 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_command 0ms
2015-12-04T10:47:11.960-0500 I COMMAND  [conn1] command test.c command: getMore { getMore: 18886010290, collection: "c", batchSize: 2.0 } ntoreturn:1 ntoskip:0 keyUpdates:0 writeConflicts:0 numYields:0 reslen:120 locks:{ Global: { acquireCount: { r: 2 } }, Database: { acquireCount: { r: 1 } }, Collection: { acquireCount: { r: 1 } } } protocol:op_command 0ms



 Comments   
Comment by J Rassi [ 08/Jan/16 ]

Closing as Won't Fix. The approach decided on in SERVER-21776 was to make the per-operation log line be in the COMMAND log component, regardless of the subsystem associated with the particular command.

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