[SERVER-27799] apply setParameter for maxSyncSourceLagSecs to slave 2 only in maxSyncSourceLagSecs.js Created: 24/Jan/17  Updated: 05/Apr/17  Resolved: 24/Jan/17

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

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   

We can stabilize the test by selectively apply change maxSyncSourceLagSecs on slave 2 only instead of both slaves 1 and 2.

---- update —
maxSyncSourceLagSecs.js changes how the secondaries sync from one another. It is appropriate to use the fail point introduced in SERVER-27231 to stabilize the test.



 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-27799 fixed maxSyncSourceLagSecs.js so that maxSyncSourceLagSecs is changed on slave 2 only instead of all nodes

(cherry picked from commit 981bd654b74fac78b1fd7334821f0f6b7e812ee3)
Branch: v3.4
https://github.com/mongodb/mongo/commit/1e942dfe6b8759c71bfad9e6200b3d2c093f89d1

Comment by Githook User [ 24/Jan/17 ]

Author:

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

Message: SERVER-27799 fixed maxSyncSourceLagSecs.js so that maxSyncSourceLagSecs is changed on slave 2 only instead of all nodes
Branch: master
https://github.com/mongodb/mongo/commit/981bd654b74fac78b1fd7334821f0f6b7e812ee3

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