[SERVER-77686] rename collection no longer logs on the changelogs the commit event Created: 01/Jun/23  Updated: 29/Oct/23  Resolved: 16/Jun/23

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

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

Issue Links:
Backports
Problem/Incident
is caused by SERVER-74192 DDL coordinators that rely on the int... Closed
Assigned Teams:
Sharding EMEA
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0
Sprint: Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26
Participants:

 Description   

After SERVER-74192 the rename collection commit on sharding catalog now runs on a remote transaction executed by the coordinator.

However, since we're not calling anymore ShardingCatalogManager::renameShardedMetadata, we no longer insert on the changelogs the commit event. This ticket is to evaluate whether to let the coordinator log such events in order to keep the logging behavior consistent with previous versions.



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

Author:

{'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-77686 added back sharding logs to rename metadata commit

(cherry picked from commit b5eec4b229cc1b7c04f04ec5a719aae814e2b4ad)
Branch: v7.0
https://github.com/mongodb/mongo/commit/0a32a1f23d6efff79315ed135a7e47b4ecb68799

Comment by Githook User [ 15/Jun/23 ]

Author:

{'name': 'Enrico', 'email': 'enrico.golfieri@mongodb.com', 'username': 'enricogolfieri'}

Message: SERVER-77686 added back sharding logs to rename metadata commit
Branch: master
https://github.com/mongodb/mongo/commit/b5eec4b229cc1b7c04f04ec5a719aae814e2b4ad

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