Mongodb always creates the mongodb.lock file when the server starts and drops it before mongodb is stopped. Removing mongodb.lock does not affect any data it just means that mongodb was not stopped correctly. So, you are correct in removing this file and running with the -repair option should fix database.
mongoimport is intended to run in command prompt and not in the mongo shell. Try exiting out of the shell and running the command.
As long as you can guarantee uniqueness, you’re not constrained to using the default “_id” MongoDB supplies. Therefore, it’s down to you how you generate this number. If you’d like to store this number inside MongoDB, then you could store it in a separate collection and increment it for every new URL required. Incrementing a … Read more
Check out the thread on the JIRA ticket that increased the value from 4MB to 16MB. There is a sizeable debate on the ticket: https://jira.mongodb.org/browse/SERVER-431 It seems to be arbitrary why they chose 16MB, and not say 32MB. It was increased because many people needed to store documents larger than 4MB (and I presume lower … Read more
Authentication prevents you from performing actions on the database (as your screenshot shows – you can’t even list databases), it doesn’t prevent connections – after all, you have to be able to connect to be able to authenticate. There is a feature request to add timeouts, but for now this is essentially how the server … Read more
I suppose what you need is: db.collection.find( { field1: { $elemMatch: { one: 1 } } } ); http://docs.mongodb.org/manual/reference/operator/elemMatch/#op._S_elemMatch
After a lot of trouble, experimenting mongo shell I’ve finally got a solution to my question. Psudocode: # To get the list of customer whose score is greater than 2000 cust_to_clear=db.col.aggregate( {$match:{$or:[{status:’A’},{status:’B’}]}}, {$group:{_id:’$cust_id’,total:{$sum:’$score’}}}, {$match:{total:{$gt:500}}}) # To loop through the result fetched from above code and update the clear cust_to_clear.result.forEach ( function(x) { db.col.update({cust_id:x._id},{$set:{clear:’Yes’}},{multi:true}); } ) … Read more
They are not random and can be easily predicted : A BSON ObjectID is a 12-byte value consisting of a 4-byte timestamp (seconds since epoch), a 3-byte machine id, a 2-byte process id, and a 3-byte counter http://www.mongodb.org/display/DOCS/Object+IDs
You can do that in 2 steps: var objIdMin = ObjectId(Math.floor((new Date(‘1990/10/10’))/1000).toString(16) + “000 0000000000000”) var objIdMax = ObjectId(Math.floor((new Date(‘2011/10/22’))/1000).toString(16) + “000 0000000000000”) db.myCollection.find({_id:{$gt: objIdMin, $lt: objIdMax}}) or in one step (what is less readable): db.myCollection.find({_id:{$gt: ObjectId(Math.floor((new Date(‘1990/10/10’))/1000).toString(16) + “000 0000000000000”), $lt: ObjectId(Math.floor((new Date(‘2011/10/10’))/1000).toString(16) + “000 0000000000000”)}})
I would store it in the order you want it back out. Or sort it after you pull it out, on the client side. If neither of those are possible, you can use the aggregation framework: > db.test.insert({answers: [ … {name: ‘paul’, state: ‘RU’}, … {name: ‘steve’, state: ‘US’}, … {name: ‘mike’, state: ‘DE’}]}); > … Read more