[SERVER-2875] Multiple dbpath, and by object assignment Created: 30/Mar/11  Updated: 21/Jul/11  Resolved: 21/Jul/11

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

Type: New Feature Priority: Major - P3
Reporter: Kenny Gorman Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-965 Store the indexes of a collection on ... Closed
Participants:

 Description   

It would be nice to be able to utilize more than one dbpath. This is for ease of expansion, but also for optimization where we want to put indexes on SSD. Each collection, and index should be able to be placed into a specific dbpath

dbpath=[/mount1, /mount2, /mount3]

  • We should be able to add a new dbpath entry on a running DB.
  • Allow for objects to be allocated to a specific datadir (collection creation, index creation, capped collection creation, gridFS)

These options allow for flexible growth because OPS folks can add more storage and allow MongoDB to keep growing without interruption. This is also great for putting indexes on fast storage like SSD's.



 Comments   
Comment by Kenny Gorman [ 21/Jul/11 ]

Yes, indexes in a separate path is a good step in this direction. Closing in lieu of SERVER-965.

Comment by Eliot Horowitz (Inactive) [ 31/Mar/11 ]

Not sure we'll go that far, but we definitely want to do indexes in a different file: SERVER-965

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