alexanderzeitler.com - MongoDB development environment journal size management using mongoctl

MongoDB development environment journal size management using mongoctl | Alexander Zeitler

Alexanderzeitler.com Spined HTML

MongoDB minutiae environment periodical size management using mongoctl | Alexander Zeitler Toggle navigation Home Feed MongoDB minutiae environment periodical size management using mongoctl Written on January 26, 2015 On a developer machine you might have to install multiple versions of MongoDB or you might want to run multiple MongoDB server instances. Both can be washed-up hands using mongoctl. To install mongoctl on Ubuntu, just run: sudo pip install mongoctl In specimen you don't have installed pip, just run this surpassing the whilom command: git clone https://github.com/pypa/pip.git cd pip python setup.py install #might need sudo / root To install the latest stable MongoDB release just run: mongoctl install-mongodb Beside installing MongoDB this moreover creates the config file for your first MongoDB server name "MyServer". You can simply start it using mongoctl start MyServer Stopping is as easy as starting it: mongoctl stop MyServer By default, journaling is enabled for MongoDB and may eat your nonflexible disk if you're running many MongoDB servers. Having installed MongoDB using mongoctl, the periodical of "MyServer" can be found here: ~/mongodb-data/my-server/journal Listing the directory content shows us, that our instance uses 3GB of nonflexible disk space. drwxrwxr-x 2 alexzeitler alexzeitler 4,0K Jan 25 00:09 . drwxrwxr-x 10 alexzeitler alexzeitler 4,0K Jan 24 23:15 .. -rw------- 1 alexzeitler alexzeitler 1,0G Jan 25 00:09 prealloc.0 -rw------- 1 alexzeitler alexzeitler 1,0G Nov 25 13:04 prealloc.1 -rw------- 1 alexzeitler alexzeitler 1,0G Nov 25 13:04 prealloc.2 While (until the 2.0 release) disabling the periodical is a bad idea for production, it is ok for a minutiae environment. To disable the journaling for "MyServer", throne over to ~/.mongoctl and edit the servers.config file. No find the "MyServer" configuration, which should be the first entry and squint like this: { "_id": "MyServer", "description" : "My server (single mongod)", "cmdOptions": { "port": 27017, "dbpath": "~/mongodb-data/my-server", "directoryperdb": true } } In order to disable MongoDB journaling, add the nojournal property to cmdOptions: { "_id": "MyServer", "description" : "My server (single mongod)", "cmdOptions": { "port": 27017, "dbpath": "~/mongodb-data/my-server", "directoryperdb": true, "nojournal" : true } } No, stop your "MyServer" instance and delete the files from the ~/mongodb-data/my-server/journal (you're doing this at your own risk, of undertow - and as said not in a production environment!) directory. After starting "MyServer" again, the periodical folder should stay empty. That's it! You can moreover limit the periodical file size to 128MB by setting the smallfiles property to true. Please enable JavaScript to view the comments powered by Disqus. Copyright © Alexander Zeitler 2003 - 2016 | Impressum