[SERVER-26106] Raise oplog socket timeout for rollback Created: 14/Sep/16  Updated: 04/Jan/17  Resolved: 15/Sep/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.2.12, 3.3.14

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-19605 Oplog timeout should be configurable Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Repl 2016-09-19
Participants:

 Description   

It is currently 30 seconds, which is not the same as any other timeout we currently use, and is too short. It should be raised to at least the timeout of the originating find command (1 minute) and probably much more in excess of that – perhaps 10 minutes.



 Comments   
Comment by Githook User [ 04/Jan/17 ]

Author:

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

Message: SERVER-26106 raise oplog socket timeout for rollback
Branch: v3.2
https://github.com/mongodb/mongo/commit/6f9314992e5a5c320a84fd3c40ad3f84cacab32b

Comment by Githook User [ 15/Sep/16 ]

Author:

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

Message: SERVER-26106 raise oplog socket timeout for rollback
Branch: master
https://github.com/mongodb/mongo/commit/1116c9d3d903e103d2fc6c3ce792134808cc8691

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