[SERVER-63461] Disable directoryPerDb(and directoryForIndexes) for serverless Created: 08/Feb/22 Updated: 20/Mar/23 Resolved: 20/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Sophia Tan | Assignee: | [DO NOT USE] Backlog - Server Serverless (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Serverless
|
| Participants: |
| Description |
|
Serverless doesn't use directoryPerDb (or directoryForIndexes) because it's not really necessary. The reason can be found from the comment (https://jira.mongodb.org/browse/CS-30369?focusedCommentId=1256870&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1256870) and confirmed with Eric that the main reason people use directoryPerDb is for better performance. |
| Comments |
| Comment by Didier Nadeau [ 20/Mar/23 ] |
|
Closing this issue as 'won't do' because cloud does not ever run the `directoryPerDb` command in Atlas and has no plan to do so in the future. |
| Comment by Didier Nadeau [ 20/Mar/23 ] |
|
didier.nadeau@mongodb.com to check with Cloud if they are aware they can't run directoryPerDb in serverless deployments. |