[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: |
|
||||||||||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
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 |