[SERVER-33547] remove backwards compatibility check for shardVersion on OSS in splitChunk Created: 28/Feb/18  Updated: 29/Oct/23  Resolved: 01/Mar/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.2
Fix Version/s: 3.7.3

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2018-03-12
Participants:

 Description   

The shardVersion field was used to pass the epoch, but in 3.6, we started explicitly sending an "epoch" field. Now that 3.6 is released, we no longer need to check the shardVersion for backwards compatibility.



 Comments   
Comment by Githook User [ 01/Mar/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-33547 fix for split_against_shard_with_invalid_split_points.js
Branch: master
https://github.com/mongodb/mongo/commit/67af2fc406b8e9118ae66fb9bb17e72a77850b83

Comment by Githook User [ 01/Mar/18 ]

Author:

{'email': 'esha.maharishi@mongodb.com', 'name': 'Esha Maharishi', 'username': 'EshaMaharishi'}

Message: SERVER-33547 remove backwards compatibility check for shardVersion on OSS in splitChunk
Branch: master
https://github.com/mongodb/mongo/commit/39730f6fe7212761b86aa2308c0e128d58b0a656

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