[SERVER-19665] Find and getMore commands should use a default timeout of 1 second for tailable, awaitData cursors Created: 30/Jul/15  Updated: 19/Sep/15  Resolved: 31/Jul/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 3.1.7

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Qingyang Chen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 7
Participants:

 Description   

Currently, when you issue a getMore on a tailable, awaitData cursor, the client must supply a maxTimeMS value. This maxTimeMS is used as the timeout while blocking and waiting for more data. If not supplied, the server will fail the query.

Instead, the server should use a default timeout of 1 second if maxTimeMS is not supplied on the getMore.



 Comments   
Comment by Githook User [ 31/Jul/15 ]

Author:

{u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}

Message: SERVER-19665 Find/getMore cmd use default maxTimeMS of 1s for tailable+awaitData cursors
Branch: master
https://github.com/mongodb/mongo/commit/8a968594237b0b5aeea809f07e7d3c7b0145cb05

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