[SERVER-80462] Avoid refreshing database cache under DDL lock upon DB creation Created: 28/Aug/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: | |
| Story Points: | 2 |
| Description |
|
In shardingCatalogManager::createDatabase() the DDL lock is held while the config server is running the _flushDatabaseCacheUpdates command is being run on the shard. The goal of this ticket is to investigate if it is safe to perform the refresh outside the database DDL lock scope. |