[SERVER-26265] Test that 3.2 mongos fails to join a featureCompatibilityVersion("3.4") cluster Created: 22/Sep/16  Updated: 19/Nov/16  Resolved: 12/Oct/16

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 3.4.0-rc1

Type: Bug Priority: Major - P3
Reporter: David Storch Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-26264 Make 3.2 mongos fail gracefully on st... Closed
Related
is related to SERVER-25158 Prevent a 3.2 mongos from joining a f... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2016-10-10, Query 2016-10-31
Participants:

 Description   

Once SERVER-26264 is complete, a 3.2 mongos process will quickly exit with an error status if you point it at 3.4 config servers with featureCompatibilityVersion "3.4". We should write a test in the multiVersion suite to verify this behavior. The test should perform the following steps:

  1. Start an all 3.4 sharded cluster.
  2. Verify that the feature compatibility version is "3.4".
  3. Assert that a new 3.2 mongos fails to start up when joining the cluster.
  4. Set the feature compatibility version to "3.2".
  5. Assert that a 3.2 mongos can now start up against the cluster and can perform reads and writes to the shards.


 Comments   
Comment by Githook User [ 10/Oct/16 ]

Author:

{u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria.vankeulen@mongodb.com'}

Message: SERVER-26265 Add tests for 3.2 mongos joining 3.4 clusters
Branch: master
https://github.com/mongodb/mongo/commit/fadd01e32d40f1e72f062de1864a7cb631ee17fa

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