[SERVER-58990] Resharding always write new collection timestamp Created: 01/Aug/21  Updated: 29/Oct/23  Resolved: 03/Aug/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 5.0.1
Fix Version/s: 5.0.4, 5.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v5.0
Sprint: Sharding EMEA 2021-08-09
Participants:

 Description   

In SERVER-58589 we removed the ShardingFullDDLSupportTimestampedVersion flag so that we always use timestamps in collection metadata.

We forgot to cleanup some resharding code that still support the old metadata format. In particular the writeDecisionPersistedState still accepts a boost:optional<Timestamp> when there must not be a case in which we don't have an actual timestamp.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 01/Oct/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-58990 Resharding always write new collection timestamp
Branch: v5.0
https://github.com/mongodb/mongo/commit/8c15aef15ffc73ff674b4631c129a4108dd5a4c9

Comment by Githook User [ 03/Aug/21 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-58990 Resharding always write new collection timestamp
Branch: master
https://github.com/mongodb/mongo/commit/f4fc6da51f438c418d75d726ba62cf04a72d6e58

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