New answers tagged

0

So turns out if you remove a mongodb cartridge after it has been deployed alongside the web servers cartridges and then replace the mongodb cartridge the web server variables don't get updated. I needed to restart the web tier servers in order for them to the get the new mongodb setting variables updated.


0

1) What is the RAM usage of your VPS? If it is running peak, you probably need to upgrade it. 2) WHat is the disk I/O when you say it is running 100%. Some provider limits IOPs which turns into lower disk I/O performance. 3) If above are fine, mongoperf and mongotop will be the option for you to start troubleshooting with ...


0

You can use query.explain() on individual queries to return the query plan for that query. You can look into that further here. https://docs.mongodb.com/manual/reference/method/cursor.explain/ Other things you might want to look into : In the output of serverStatus: scanned scanAndOrder In the output of collStats: totalIndexSize indexSizes In the ...


0

The snapshot process shouldn't be visible to the instance. The real problem would come when you try to restore from the "unclean" snapshot. If a process is writing to the volume (or rather, to an open file descriptor for a file on the volume), write requests in the instance's kernel cache may not be written to disk, or may only be partially written. These ...


1

Yes that is normal. Mongodb pre-allocates blocks of data for writes to happen. This allows it to handle more write operations without taxing your disk. Take a look at the following for more information https://docs.mongodb.com/manual/faq/storage/#faq-disk-size


1

When you call pecl binary without full path your shell likely runs /usr/bin/pecl, which in turn is likely installed by PHP5 from a .deb package. You need to run the pecl binary installed with PHP7. Where is it placed it can only be known for sure by you as paths are configured at compile time. Try /usr/local/bin/pecl and $PREFIX/bin/pecl ($PREFIX being ...


0

the user should be added in the admin database so like this: RUN mongod --fork --logpath /var/log/mongodb.log \ && sleep 5 && mongo foobar /tmp/create_ddbb.js


0

There is a read preference value "nearest" which actually uses the latency between the MongoS and MongoD to determine which is the best/fastest set member for the query. You can find the documentation about it here: https://docs.mongodb.org/manual/reference/read-preference/#nearest The selection is based on the "member selection". For a sharded cluster like ...



Top 50 recent answers are included