Tag Info

Hot answers tagged

2

Original Answer (leaving for people that might hit this because of the simple explanation): The clusterAdmin role only applies when you authenticate against the admin database, so unless you specify the --authenticationDatabase option to be admin when you are running mongodump/mongorestore I suspect you are getting a lesser privilege when authing against ...


2

As an answer to your first question, both tools (by default) will just walk the _id index to fetch the data and then write it out to disk. So, yes, both tools will similarly impact your working set which is why I would generally recommend running them against a secondary (preferably a hidden secondary if possible). I'll echo Stennie in the comments here ...


2

(sorry, dunno) --query will select or exclude entire documents, not fields. It would be a good idea though : --query '{datetime:{$gt:ISODate("2014-01-01T00:00:00.000Z")}},{_id:0,name:1,address:1,interests:1}'* ) Mongodump uses bson file structure and preserves the data types. Mongoexport will lose data type of the values. Such as ...


2

I think I found my answer from the mongoDB manual: In general, use embedded data models when: you have “contains” relationships between entities. See Model One-to-One Relationships with Embedded Documents. you have one-to-many relationships between entities. In these relationships the “many” or child documents always appear with or are viewed in the ...


1

Easiest way to find the storage engine being used currently in linux. Inside mongo console type db.serverStatus().storageEngine It returns the storage engine being used currently { "name" : "wiredTiger" } Once it is confirmed that wiredTiger is being used then type db.serverStatus().wiredTiger to get all the configuration details of wiredTiger.


1

This is the same issue as described here (for MySQL): High CPU usage from MySQL with no queries at all running sudo date -s now Caused by leap second and a bug in the kernel.


1

To migrate data between different storage engines in MongoDB 3.0 you will need to perform an initial sync to the new replica set node or use mongorestore to seed a new replica set with your data. If you want to add a node with a new storage engine to a live production replica set, rs.add() is the correct approach. To ensure a smooth upgrade I would also ...


1

You are not using the correct index. The current index will bring the results sorted but it have to perform a full collection scan. You need an index like: {"category_memberships.node":1,"ships_to_australia":1,"ps":1,"salesRate":-1} that limits the search and sorts at the same time. The query execution variation has to do with the hotset and collection ...



Only top voted, non community-wiki answers of a minimum length are eligible