[SERVER-71615] Add top-level `onCurrentShardSince` field to `config.chunk` entries Created: 25/Nov/22  Updated: 29/Oct/23  Resolved: 21/Dec/22

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
is depended on by SERVER-71616 Add `onCurrentShardSince` top-level f... Closed
is depended on by SERVER-71617 Remove `validAfter` top-level field f... Closed
is depended on by SERVER-72283 Take into account mergeability constr... Closed
Problem/Incident
causes SERVER-72360 Make sure `history` ChunkType field i... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26
Participants:
Linked BF Score: 161

 Description   

The history field on config.chunks holds an array of objects in the following format:

{validAfter: Timestamp(12345), shard: "shardName"} 

The auto-merger will be expected to act based on the value of the higher validAfter present in the history, but indexing arrays can be much more inefficient than indexing top-level fields. In order to avoid performance issues, purpose of this ticket is to add the same field also at the top-level.



 Comments   
Comment by Githook User [ 21/Dec/22 ]

Author:

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

Message: SERVER-71615 Add top-level `onCurrentShardSince` field to `config.chunk` entries
Branch: master
https://github.com/mongodb/mongo/commit/82c46f01769d6cbae70a27ff948b0d93c49f7420

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