[SERVER-47662] Make ClusterWriter only send databaseVersion if in FCV 4.4 Created: 20/Apr/20  Updated: 29/Oct/23  Resolved: 21/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.4.0-rc3

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2020-05-04
Participants:
Linked BF Score: 50

 Description   

In v4.4, we started attaching the database version to the write path. A v4.4 mongod can route a write to a v4.2 mongod as a part of a $merge and if this happens the v4.4 mongod will attach a database version. If the v4.2 mongod is stale, it will throw StaleDbVersion and should refresh.

Note that in most cases, mongos is the one to route to a shard and it should always be at the same or a lower version than any mongod(s), so this is only a problem with a v4.4 mongod routes to a v4.2 mongod.



 Comments   
Comment by Githook User [ 21/Apr/20 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-47662 Make ClusterWriter only send databaseVersion if in FCV 4.4
Branch: v4.4
https://github.com/mongodb/mongo/commit/64887950d31381a431571b09abd31ec0e05c06e1

Comment by Esha Maharishi (Inactive) [ 20/Apr/20 ]

As part of this, we should also unblacklist the tests that were blacklisted in SERVER-45145.

Generated at Thu Feb 08 05:14:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.