[SERVER-20800] getMore command against awaitData cursor does not block Created: 07/Oct/15  Updated: 15/Oct/15  Resolved: 08/Oct/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 3.1.9
Fix Version/s: 3.2.0-rc0

Type: Bug Priority: Critical - P2
Reporter: David Storch Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-20604 CSRS with protocol version 1 is slow ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

In a 3.1.9 shell (or an earlier shell with --readMode commands):

db.c.drop()
db.createCollection("c", {capped: true, size: 1024});
db.c.insert({_id: 1});
db.c.find().addOption(DBQuery.Option.tailable).addOption(DBQuery.Option.awaitData);

Sprint: RPL A (10/09/15)
Participants:

 Description   

This is a regression introduced under SERVER-20604 in commit https://github.com/mongodb/mongo/commit/a8e6c0ebc70fad95a5e05281076cfa4b6db500c2. It affects only the getMore command, not OP_GET_MORE. Affects only development release 3.1.9.



 Comments   
Comment by Githook User [ 08/Oct/15 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-20800 block AwaitData if no lastCommitOpTime provided in query parameters.
Branch: master
https://github.com/mongodb/mongo/commit/c88c5b169d9d21eb01f3b0547c8cc4ad0228c358

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