[SERVER-32910] Update multiVersion/feature_compatibility_version_lagging_secondary.js to use v3.6 and v4.0 binaries, rather than v3.4 and v4.0 Created: 25/Jan/18  Updated: 23/Feb/18  Resolved: 23/Feb/18

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Maria van Keulen
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32636 Close outgoing connections to servers... Closed
Sprint: Storage 2018-02-26
Participants:

 Description   

This depends on SERVER-32636 to be completed first, as it will make v3.6 nodes fail to communicate with v4.0 nodes when FCV 4.0 gets set.

Currently, multiVersion/feature_compatibility_version_lagging_secondary.js still runs successfully because it is explicitly testing v3.4 nodes with latest (v4.0) nodes.



 Comments   
Comment by Maria van Keulen [ 23/Feb/18 ]

This work will be done as part of SERVER-32636, as it constitutes testing for the aforementioned ticket.

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