[SERVER-22300] Perform manual testing to understand the failure mode when an old v3.0 mongos is running with a cluster in CSRS mode Created: 25/Jan/16  Updated: 05/Feb/16  Resolved: 26/Jan/16

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: csrsupgrade
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding F (01/29/16)
Participants:

 Description   

Two cases that come to mind that we want to make sure to verify fail in reasonable ways are:

  • A 3.0 mongos started before the upgrade to CSRS, what happens after upgrading to CSRS and you try to use it
  • a 3.0 mongos pointing at 3 CSRS config servers, but using an SCCC connection string.


 Comments   
Comment by Esha Maharishi (Inactive) [ 25/Jan/16 ]

Confirming that "use" a mongos is covered by:

  • capturing the output of the mongos process
  • connecting to it from a 3.0 mongo shell
  • connecting to it from a 3.2 mongo shell

?

Comment by Esha Maharishi (Inactive) [ 25/Jan/16 ]

Yup on it

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