[SERVER-28005] Oplog query network timeout is less than the maxTimeMs Created: 14/Feb/17  Updated: 27/Aug/18  Resolved: 15/Feb/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.13, 3.4.3, 3.5.4

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-19605 Oplog timeout should be configurable Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.4, v3.2
Sprint: Repl 2017-02-13, Repl 2017-03-06
Participants:
Case:

 Description   

Currently the initial find for the GTE query on the oplog has a 60 second maxTimeMs, and the subsequent getMores have a maxTimeMs equal to the election timeout / 2. Both the find and the getMore, however, have timeout from the networking subsystem equal to the election timeout. Given the default election timeout is 10 seconds, that means if the initial find takes more than 10 seconds to find the common point in the oplog and return the first batch it will time out, rather than waiting the 60 seconds of the maxTimeMs.

This can make it hard for nodes that have high repl lag to catch up, as if the common point in the oplog is far back, it could consistently take more than 10 seconds, which would leave the node unable to start replicating.



 Comments   
Comment by Michael Brenden [ 25/Jul/17 ]

We suffered this until 3.4.3.
More here https://jira.mongodb.org/browse/SERVER-19605

Comment by Githook User [ 02/Mar/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-28005 Increase network timeout on oplog queries to be larger than the maxTimeMs

Manually performed backport for 3.2 of f6006942e76377c9434a61e76a7803eb83430591
Branch: v3.2
https://github.com/mongodb/mongo/commit/f0505a8532a60c6ef1a0f1194604910b413105cf

Comment by Githook User [ 02/Mar/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-28005 Increase network timeout on oplog queries to be larger than the maxTimeMs

(cherry picked from commit f6006942e76377c9434a61e76a7803eb83430591)
Branch: v3.4
https://github.com/mongodb/mongo/commit/633a7101f5c0c21ef895b92c695dee9f012bbefc

Comment by Githook User [ 15/Feb/17 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-28005 Increase network timeout on oplog queries to be larger than the maxTimeMs
Branch: master
https://github.com/mongodb/mongo/commit/f6006942e76377c9434a61e76a7803eb83430591

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