[SERVER-13179] 2.6 mongos should warn or error when connecting to too old shards Created: 12/Mar/14  Updated: 10/Dec/14  Resolved: 02/May/14

Status: Closed
Project: Core Server
Component/s: Sharding, Usability
Affects Version/s: 2.6.0-rc1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Mathias Stearn Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Using a 2.6 mongos with shards older than 2.4.10 is dangerous since it can lead to ignored writeconcerns.



 Comments   
Comment by Greg Studer [ 02/May/14 ]

We do this - there's a version check for config upgrade.

Comment by Spencer Brody (Inactive) [ 12/Mar/14 ]

Does that mean to upgrade to 2.6 users on 2.4.9 will need to upgrade to 2.4.10 first?

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