[SERVER-71616] Add `onCurrentShardSince` top-level field to `config.chunk` entries on upgrade Created: 25/Nov/22  Updated: 29/Oct/23  Resolved: 16/Jan/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.3.0-rc0

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

Issue Links:
Depends
depends on SERVER-71615 Add top-level `onCurrentShardSince` f... Closed
is depended on by SERVER-71617 Remove `validAfter` top-level field f... Closed
Related
is related to SERVER-72791 Remove upgrade procedure for adding o... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23
Participants:

 Description   

When coming from a version not including the changes from SERVER-71615, config.chunks entries must be updated on upgrade in order to comply with the new format.

As we don't plan to clear the onCurrentShardSince field on downgrade, existing values of such field must be overridden with the top of the history (just to be sure).



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

Author:

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

Message: SERVER-71616 Add `onCurrentShardSince` top-level field to `config.chunk` entries on upgrade
Branch: master
https://github.com/mongodb/mongo/commit/708be04d957045dc94673d32be87632044141f0d

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