[DRIVERS-1315] Set minWireVersion to 6 (MongoDB 3.6) Created: 02/Jul/20 Updated: 05/Apr/23 Resolved: 22/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Rachelle Palmer | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Quarter: | FY22Q3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Detailed Project Statuses: | Lead: Bernie 2021-09-24:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
SummaryWith the introduction of the versioned API in MongoDB 5.0 it is possible to remove support for very old server versions without breaking the rule "upgrading from server version A to server version X must require no more than one driver version upgrade". MongoDB 3.4 reached end of life in January of 2020. MongoDB 3.6 (which reached end of life in April 2021, but seems likely to still exist in Atlas for some time) introduced OP_MSG, which replaced the previous wire protocol for MongoDB. 3.6 seems like the right new minimum server version. MotivationWho is the affected end user?Users that are on any server versions earlier than 3.6 will no longer receive driver support. This will not impact users that are on 3.6 or later. How does this affect the end user?Users on anything earlier than 3.6 will need to either upgrade to a newer server version or be content with lack of modern driver support. How likely is it that this problem or use case will occur?Based on usage analysis, we believe that dropping support for 3.4 and earlier is the right decision as most users are on 3.6+ and we stand to see significant efficiency gains by dropping support. If the problem does occur, what are the consequences and how severe are they?Users will need to upgrade to a newer server version if they would like to receive modern driver support. Is this issue urgent?This is a significant decision, so achieving clarity on our cross-org stance is critical. Is this ticket required by a downstream team?This has implicit cross-org consequences, so much of this project's early effort will be establishing clarity and agreement across organizations. Is this ticket only for tests?No. Cast of CharactersEngineering Lead: Bernie Hackett Channels & DocsSlack ChannelScope DocumentTechnical Design Document |
| Comments |
| Comment by Jeffrey Yemin [ 13/Jul/21 ] |
|
It looks like the Atlas clusters we use for connectivity tests are pinned to MongoDB 3.4. They will need to be upgraded or replaced. |
| Comment by Jeremy Mikola [ 08/Jul/21 ] |
|
Changing existing "depends on" language tickets to "is related to", since this issue was repurposed to drop support for MongoDB 3.4 and earlier. |