Mongodb

Changing the storage engine for a standalone MongoDB server from Mmapv1 to WiredTiger is relatively painless. Here’s how I did it. Backup the database mongodump --out /srv/backup/mongodb Stop monbodb service service mongodb stop Update mongodb.conf. Here’s my /etc/mongodb.conf file: # mongod.conf storage: dbPath: "/var/lib/mongo" engine: wiredTiger wiredTiger: engineConfig: cacheSizeGB: 1 statisticsLogDelaySecs: 0 journalCompressor: snappy directoryForIndexes: false collectionConfig: blockCompressor: snappy indexConfig: prefixCompression: true systemLog: verbosity: 1 path: "/var/log/mongodb/mongod.log" logAppend: true logRotate: reopen destination: file timeStampFormat: iso8601-utc processManagement: fork: true pidFilePath: "/var/run/mongodb/mongod.pid" net: bindIp: 127.0.0.1 port: 27017 wireObjectCheck: false unixDomainSocket: enabled: true Start monbodb service ...

After upgrading MongoDB from version 2.4 to 2.6, I am not able to connect to it from another machine. The firewall has been checked to ensure that port 27017 is opened for the machine that I want to connect from. So what else could go wrong? Well, I was impatient and turned to you know what… Google search. According to this link: https://groups.google.com/forum/#!msg/mongodb-user/yhf05AW-hK8/YqES0cVIXlUJ, the problem is due to the database is bound to only local IP. ...