[SERVER-25752] Adjust jstests to deal with setFeatureCompatibilityVersion write after first election Created: 23/Aug/16  Updated: 27/Jan/17  Resolved: 19/Sep/16

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

Type: Task Priority: Critical - P2
Reporter: Scott Hernandez (Inactive) Assignee: Scott Hernandez (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-25155 Create setFeatureCompatibilityVersion... Closed
Sprint: Repl 2016-08-29, Repl 2016-09-19
Participants:
Linked BF Score: 0

 Description   

Now that a document is written into a new database after the first election, replication can be delayed for our testing.

This is not a production/user problem but simply an issue with the timing (and timeouts set) in our tests.



 Comments   
Comment by Scott Hernandez (Inactive) [ 19/Sep/16 ]

Master/Slave tests have stabilized with other changes.

Comment by Scott Hernandez (Inactive) [ 24/Aug/16 ]

For replica sets we have moved this documents creation to the time of the repl set creation (initiate call) but master/slave tests might still need to be worked on.

Comment by Eric Milkie [ 23/Aug/16 ]

Considering instead to change the time when we do the write, to avoid hitting timeouts during jstest elections.

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