[SERVER-72533] Shards must send `validAfter` field on _configsvrCommitChunksMerge on v6.0 Created: 05/Jan/23  Updated: 29/Oct/23  Resolved: 05/Jan/23

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

Type: Bug Priority: Major - P3
Reporter: Silvia Surroca Assignee: Silvia Surroca
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Problem/Incident
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-01-09
Participants:
Linked BF Score: 156

 Description   

After backporting SERVER-71479 to v6.0 (BACKPORT-14282) we may have a scenario where the shard is not including the `validAfter` field on `_configsvrCommitChunksMerge` command, while the config server expects it. In that case command fails with error message "chunk operation requires validAfter timestamp"

This happens only when config server has a version that doesn't include the SERVER-71479 feature while shard does. Since the config server is upgraded before shards on a cluster upgrade, this was not needed on master. It is needed on backporting tickets though because, for instance, we can upgrade from v6.0 (which has the feature SERVER-71479) to v6.1 (which doesn't).



 Comments   
Comment by Githook User [ 05/Jan/23 ]

Author:

{'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}

Message: SERVER-72533 Shards must send `validAfter` field on _configsvrCommitChunksMerge on v6.0
Branch: v6.0
https://github.com/mongodb/mongo/commit/8ce31326668592d9121897bd777d017dd24a6fee

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