[SERVER-27847] increase timeout in apply_batch_only_goes_forward.js Created: 27/Jan/17  Updated: 05/Apr/17  Resolved: 27/Jan/17

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

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Repl 2017-02-13
Participants:
Linked BF Score: 0

 Description   

On slow machines, we should wait longer for the

{w: 2}

write operation to propagate to the two data bearing nodes without the modified minValid entry. The current timeout is 90 seconds. The default ReplSetTest timeout of 10 minutes should be more than sufficient.



 Comments   
Comment by Githook User [ 08/Feb/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-27847 increase timeout in apply_batch_only_goes_forward.js

(cherry picked from commit a12ae9bdaaf25aea73c181ddfcde9c4be38dda80)
Branch: v3.4
https://github.com/mongodb/mongo/commit/c7a3aa3b19f0514c7d946ab27e1521f99b1c118d

Comment by Githook User [ 27/Jan/17 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-27847 increase timeout in apply_batch_only_goes_forward.js
Branch: master
https://github.com/mongodb/mongo/commit/a12ae9bdaaf25aea73c181ddfcde9c4be38dda80

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