[SERVER-74719] Optimise the execution time of RenameCollectionParticipantService Created: 09/Mar/23  Updated: 25/May/23  Resolved: 25/May/23

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

Type: Improvement Priority: Major - P3
Reporter: Paolo Polato Assignee: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by SERVER-71365 nss.rename(newNss, dropTarget) should... Closed
Related
related to SERVER-77492 Complete TODO listed in SERVER-74719 Blocked
Assigned Teams:
Sharding EMEA
Participants:

 Description   

SERVER-71365 introduced a new check to verify if the process participating to a sharded renameCollection is also acting as the coordinator of the DDL, which is based on a remote query to the sharding catalog.

Such remote query could be replaced with a local read of config.system.sharding_ddl_coordinators, looking for the document represents the state or the RenameCollectionCoordinator


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