[00:35:03] <enjawork> im having trouble getting indices to work right. when explaining nscanned is showing that its scanning my entire collection even tho i am specifying a limit in the options to my query
[00:38:03] <peterjohnson> hey all. have a question about clonecollection in mongodb if anyone could help!
[01:04:17] <qswz> when you search for the presence of *only* "bar" in the "foo" array, still always need the array notation? {"foo":{$in:["bar"]}
[01:49:35] <nocturne777> I think there's an issue with the author's code here: http://pastebin.ca/2492286
[01:50:55] <nocturne777> I just do not understand how the second 'update' request could result in "result['updatedExisting'] == true"
[01:51:18] <nocturne777> if it the upsert is successful, that field would be false
[03:13:50] <naillwind_> mongo db challenge. how is it possible to do an update with an $addToSet operation on a nested array? eg field, array, array. structure sample in this http://pastebin.com/Drgdiznn
[03:26:38] <quickdry21> Anyone know if a config server (1/3 for the cluster) going down (for backups), will cause pymongo to raise an AutoReconnect exception?
[03:30:18] <naillwind_> however, let me just check those suggestions.
[03:52:02] <aliceow> Hi, I'm very new to Mongodb and I have a documentation lookup question
[03:52:31] <aliceow> where can I find the documentation for db.collection('collection-name', callback)?
[03:52:48] <aliceow> where callback is: function(error, collection_retrieved)
[03:53:06] <aliceow> I found http://mongodb.github.io/node-mongodb-native/markdown-docs/collections.html#selecting-collections, but it doesn't specify what callback is
[03:53:53] <aliceow> yes, I know what db.collection is supposed to have in its arguments. The reason I'm asking for documentation is so that in the future I can refer to this source if I encounter something I don't know.
[03:55:01] <naillwind_> umm so in mongodb, is it not possible to perform an operation such as: db.collection.update({_id: doc}, { $push: { 'array.doc(where _id: abc).subarray': { _id: "123" }}}); somehow?
[04:00:30] <naillwind_> retran, thanks.. I was right on that with this as well: http://diogogmt.wordpress.com/2012/03/23/update-elementmatch-and-the-positional-operator-on-mongodbmongoose/
[04:01:21] <naillwind_> just wondered how it was possible to use it in combination with .update and $addToSet
[04:01:43] <retran> you'd use elemMatch in your update query
[04:22:56] <aliceow> nvmd guys, I found it http://mongodb.github.io/node-mongodb-native/api-generated/db.html#collection
[04:57:17] <carbonpile> does anyone have any ACL experience?
[07:10:33] <morfin> as exaple user A is loading random client from database another user B should not get that client if loading random client at same time
[07:12:05] <joannac> what's a client in this context? a document?
[08:40:52] <Nilshar> Hello all, there is something I don't understand in my mongo setting. I'm using php driver to connect to a replicaset, giving to php master and slave host. all works fine when all servers are up, but if I shut down the slave host (not only the mongod, but all the host), then all connection to mongodb are slow (>3s), any idea why ?
[12:51:48] <Nilshar> Derick: thanks I'll take a look
[14:02:00] <Nilshar> Derick: very useful thanks. well, it tries to connect to the slave and block everything until timeout.
[14:15:35] <ajph> hi. i'm looking for some anecdotal information to suggest what sort of performance i might get out of mongodb on various ec2 instances. anyone mind sharing?
[19:37:26] <jergerber> thanks for the pointer, ranman.
[20:01:44] <othiym23> hello everybody, does anybody know what happened to node-mongodb-native 1.3.20?
[20:02:17] <othiym23> I got some complaints about it breaking New Relic's instrumentation for Node so I added some changes and tests to deal with the way it handled cursors, but now it's been pulled from npm
[20:02:55] <othiym23> side note: it's really irritating when packages are pulled from npm, because it means that the tests continue to pass on our dev boxes but fail in CI because CI doesn't have the pulled modules in cache
[20:03:15] <othiym23> putting out a new version of the module with whatever was bad reverted is *much* better for downstream consumers
[20:03:30] <othiym23> anyway, I'm wondering what happened there, and if I should nuke those tests, or what
[20:17:04] <ranman> othiym23 as I understand it the issue with 1.3.20 was an issue with NPM behavior not the driver
[20:51:58] <tab1293> anyone here work for mongodb?
[20:52:38] <joannac> tab1293: hrm? why do you need a mongodb employee?
[20:53:48] <tab1293> I put in an intern application and wanted to see if there was someone who I could contact to see if it was receieved
[21:06:51] <solidus-lake> hey all, i keep getting a 104 from pymongo why would this be hapening so frequently? i dont see it beign under much load
[21:07:02] <solidus-lake> what should i be paying attention to, ms of global locks?
[21:40:34] <Joeskyyy> solidus-lake: happen to know the size of the BSONs you're throwing at Mongo?
[21:41:20] <solidus-lake> Joeskyyy: no, but this is happening on a fetch is there a certain size limit i should worry about?
[21:41:39] <Joeskyyy> I believe it should be less than 16MB
[21:43:28] <Joeskyyy> Someone had a similar issue here, see their resolution/calculation in the first answer: http://stackoverflow.com/questions/11498631/connection-reset-by-peer-error-in-mongodb-on-bulk-insert
[21:44:28] <Joeskyyy> I'm not 100% sure on fetches though, maybe someone else can chime in to confirm
[21:53:14] <azathoth99> do you guys have any problems cloning a production data set into staging?
[21:53:23] <azathoth99> procedure wont work for me..
[21:53:36] <azathoth99> I end up with prod replicaset in stag
[21:53:51] <azathoth99> you cant reason with it! it doesnt feel pain
[22:07:49] <skloot> I've got a shard draining that's been stuck on one chunk remaining for hours, and there's no moveChunk in progress... is that normal?