[SERVER-20916] don't know how to specify wiredTiger in my config file Created: 14/Oct/15  Updated: 07/Apr/23  Resolved: 14/Oct/15

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

Type: Question Priority: Major - P3
Reporter: Christophe Blanc Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Red Hat Enterprise Linux Server release 6.6
mongodb v3.0.6
I don't know the wiredTiger version


Issue Links:
Related
Participants:

 Description   

hello,

I have a Mongodb 3.0 enterprise server, starting with Mongodb (new tool for us here in Air France) .
My problem is about wiredTiger. When I launch wiredTiger through command line, it works fine :

mongod --dbpath=/mongodb/data/MONIKA --storageEngine=wiredTiger --logpath=/mongodb/data/logs/mongod.log --port=27017

--> starts OK

..but when I put "storageEngine=wiredTiger" or "engine=wiredTiger" in the /etc/mongod.conf file , in order to use service , it doesn't work , nothing appends (except a FAILED message) , and no new lines in the mongod.log ...

Nevertheless, I read the documentation and followed it.

Without the line "storageEngine=wiredTiger" or "engine=wiredTiger" , I launch the command "service mongod start" and it works fine.

What is the syntax to use wiredTiger in a config file ?

thanks,
Christophe



 Comments   
Comment by Ramon Fernandez Marina [ 14/Oct/15 ]

chblanc, please take a look at the documentation for storage configuration options.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

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