[SERVER-73399] CollectionCatalog is being linked and used on MongoS Created: 27/Jan/23 Updated: 31/Jan/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Operating System: | ALL |
| Participants: |
| Description |
|
There is at least one usage of the CollectionCatalog on MongoS. This pulls storage engine code into MongoS which is supposed to be a lightweight router component only. If parts of the CollectionCatalog are necessary there (such as the profiler settings as it looks like), these should be refactored in a separate component and pulled out. |
| Comments |
| Comment by Louis Williams [ 27/Jan/23 ] |
|
It seems like the call to getDatabaseProfileSettings() always returns nullptr anyways on mongos, so we should just be able to remove that without trouble. |