[SERVER-18963] Make directory per DB the default for WT Created: 13/Jun/15  Updated: 06/Dec/22  Resolved: 15/Jun/17

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

Type: Improvement Priority: Major - P3
Reporter: Eitan Klein Assignee: Backlog - Storage Execution Team
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-18025 Option to allocate disk space headroo... Closed
Assigned Teams:
Storage Execution
Sprint: Quint Iteration 6
Participants:

 Description   

As WT use many files (e.g. LSM implementation) –directoryperdb will enable us to scale w/o hitting a limits on the amount of files per directory



 Comments   
Comment by Daniel Pasette (Inactive) [ 07/Jul/15 ]

This is really more of a cosmetic issue, than functional. Even with LSM enabled and creating possible 100x more files, this won't be a problem with file system limits in any way.

Comment by Max Hirschhorn [ 29/Jun/15 ]

1. Is there a reason not to make directory per database the default for all storage engines? The motivation would be to have the behavior of MMAPv1 and WT be consistent whenever possible.

2. Related to SERVER-17703 and SERVER-1379. Should running the dropDatabase command on WiredTiger delete the entire directory, or only the contents (i.e. remove the collection and index files)?

Generated at Thu Feb 08 03:49:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.