meteor-up
meteor-up copied to clipboard
Option to add smallfiles=true for mongodb.conf
Hi,
I'm currently running into an issue with the mongodb docker container continuously restarting with the following error message:
MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=1fd15b87c7f6
db version v3.4.1
git version: 5e103c4f5583e2566a45d740225dc250baacfbd7
OpenSSL version: OpenSSL 1.0.1t 3 May 2016
allocator: tcmalloc
modules: none
build environment:
distmod: debian81
distarch: x86_64
target_arch: x86_64
options: { config: "/mongodb.conf", storage: { dbPath: "/data/db" } }
Detected data files in /data/db created by the 'mmapv1' storage engine, so setting the active storage engine to 'mmapv1'.
journal dir=/data/db/journal
recover : no journal files present, no recovery needed
Insufficient free space for journal files
Please make at least 3379MB available in /data/db/journal or use --smallfiles
exception in initAndListen: 15926 Insufficient free space for journals, terminating
shutdown: going to close listening sockets...
removing socket file: /tmp/mongodb-27017.sock
shutdown: going to flush diaglog...
shutdown: waiting for fs preallocator...
shutdown: final commit...
shutdown: closing all files...
closeAllFiles() finished
now exiting
shutting down with code:100
When I edit the /opt/mongodb/mongodb.conf
file and add a setting smallfiles=true
the issue goes away, but on the next mup setup
the file would be overwritten and the issue would come back.
It would be really nice to be able to include a custom mongodb.conf file to overwrite the default one, or a mup.js setting e.g. mongo: { smallfiles: true }
Did you find an better way for applying smallfiles : true
?
this option was only available on MMAPv1 that is deprecated and removed since mongo 4.2. I think this issue could be closed now.