[SERVER-77540] RenameCollectionCoordinator must persist config time Created: 29/May/23  Updated: 29/Oct/23  Resolved: 14/Jun/23

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

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

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26
Participants:

 Description   

The RenameCollectionCoordinator must persist the config time after updating the collection entry. This will ensure that even in case of stepdown the next primary, during collection metadata refresh won't read stale information from the config server.



 Comments   
Comment by Githook User [ 14/Jun/23 ]

Author:

{'name': 'Pol Pinol Castuera', 'email': 'pol.pinol@mongodb.com', 'username': 'PolPinol'}

Message: SERVER-77540 Checkpoint config time after committing sharded rename
Branch: master
https://github.com/mongodb/mongo/commit/1d93d6ff677165e76bd10dd6a04a58d7ccd3e395

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