[SERVER-8430] getmore ops in db.currentOp() returns different 'query' field for mongos and mongod Created: 31/Jan/13  Updated: 16/Jul/18  Resolved: 16/Jul/18

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

Type: Bug Priority: Minor - P4
Reporter: Louisa Berger Assignee: Bernard Gorman
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Steps To Reproduce:

while a getmore op is running, run db.currentOp() and look at 'query' field for a mongod node and a mongos node.

Sprint: Query 2018-07-30
Participants:

 Description   

when db.currentOp() is run for a getmore op, the 'query' field returns { "$query" :

{ <query> } } for mongos, but { <query> }

for mongod



 Comments   
Comment by Bernard Gorman [ 16/Jul/18 ]

Confirmed, this has been fixed. Legacy getMore now upconverts the originating query to resemble a find command on both mongoD and mongoS.

Tests to verify this behaviour can be found here.

Comment by Ian Whalen (Inactive) [ 13/Jul/18 ]

Assigning to Bernard to investigate and determine if this has gone away in the next sprint.

Comment by Gregory McKeon (Inactive) [ 12/Jul/18 ]

We believe this may have been fixed - sending to query to triage.

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