[SERVER-16130] --directoryperdb under WiredTiger is not working Created: 13/Nov/14  Updated: 04/Dec/14  Resolved: 13/Nov/14

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

Type: Bug Priority: Minor - P4
Reporter: marian badinka Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on DOCS-4360 Release Notes / 2.8 docs don't mentio... Closed
Related
is related to SERVER-16132 implement directoryperdb under WiredT... Closed
Operating System: ALL
Steps To Reproduce:

mongod --dbpath . --storageEngine wiredtiger --directoryperdb

Participants:

 Description   

Mongo will not create separated directory per database. Only JOURNAL folder is created.



 Comments   
Comment by Ramon Fernandez Marina [ 04/Dec/14 ]

marian.badinka@dhl.com, --directoryperdb has been implemented for WiredTiger and is part of the 2.8.0-rc2 release candidate that got published this morning. If you give it a try please let us know if you run into any issues.

Regards,
Ramón.

Comment by Ramon Fernandez Marina [ 13/Nov/14 ]

marian.badinka@dhl.com, this is just to let you know that we've opened SERVER-16132 to implement directoryperdb in WiredTiger. Feel free to watch that ticket and vote for it.

Regards,
Ramón.

Comment by Ramon Fernandez Marina [ 13/Nov/14 ]

This is the log when I run the command above:

2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] MongoDB starting : pid=19905 port=27017 dbpath=. 64-bit host=tab
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] 
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] ** NOTE: This is a development version (2.7.9-pre-) of MongoDB.
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] **       Not recommended for production.
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] 
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] db version v2.7.9-pre-
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] git version: 92d967e8cd4d32f3b3348c89320f238df47a1454
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] build info: Linux tab 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] allocator: tcmalloc
2014-11-13T14:37:45.306-0500 I CONTROL  [initandlisten] options: { storage: { dbPath: ".", engine: "wiredtiger", mmapv1: { directoryPerDB: true } } }
==> 2014-11-13T14:37:45.306-0500 W STORAGE  [initandlisten] Detected configuration for non-active storage engine mmapv1 when current storage engine is wiredtiger
2014-11-13T14:37:45.306-0500 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=31G,session_max=20000,extensions=[local=(entry=index_collator_extension)],statistics=(all),log=(enabled=true,archive=true,path=journal),checkpoint=(wait=60,log_size=2GB),
2014-11-13T14:37:45.400-0500 I NETWORK  [initandlisten] waiting for connections on port 27017

The line marked with ==> shows the warning message, so this is expected: options that do not apply to a given storage engine are ignored, and a warning is printed on startup.

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