[08:44:53] <idank> i'm migrating my data from a single mongodb to a sharded cluster with 3 physical servers. one collection has 43 million documents and i noticed a peculiar pattern in the write performance of that collection over the last 48 hours
[08:45:44] <idank> this graph shows the iowait of the servers involved: the blue line is an average across the sharded cluster, and the green one if the single mongodb instance that i'm reading from https://dl.dropboxusercontent.com/u/18261201/iowait.jpg
[08:46:53] <idank> it seems like as the sharded collection is being filled, the cluster is waiting more for io
[08:47:53] <idank> this is the code that does the copy: https://gist.github.com/idank/5812727
[12:02:35] <Zelest> but yeah, if you havn't switched db, it's probably using "test"
[13:41:09] <spuz> hello, is it possible to query a collection that looks like this: {"Bob":23, "Bill":24, "Jill":25} to return just elements beginning with "B" or ending in "ill"?
[13:46:03] <spuz> or is the general advice to have known field names for your data?
[13:51:46] <redsand_> spuz: you'd need a map/reduce function
[13:51:53] <redsand_> i dont think aggregate functions can do that
[13:54:49] <bartzy> Derick: My weekly nag - On the PHP driver on 1.3+ , if I do $m = new MongoClient($server); and I keep the script open for a day. No timeout will occur? The connection will remain open ?
[13:54:55] <kali> spuz: it's recommended that the field names are keywords of your app, not actual data
[13:55:11] <bartzy> ah, kali, perhaps you know that piece about the PHP driver? :)
[13:55:15] <Derick> bartzy: the connection will remain open unless something closes it
[13:55:21] <kali> spuz: so you should probably refactor this as [{ name: "Bill", value: 23 }, ...]
[13:55:25] <Derick> either a replicaset failover or network interruptions
[13:55:30] <Derick> bartzy: please do upgrade to 1.4.1 though
[14:24:20] <Derick> must better replicaset handling
[14:24:32] <Derick> bartzy: and yes, the driver will only try every 60 seconds
[14:26:44] <bartzy> Derick: what has changed with replicaset handling? :D
[14:27:08] <bartzy> Derick: BTW, were you at the MongoDB Days conference in Tel Aviv? :)
[14:27:15] <idank> I posted a topic to mongodb-users like 10 hours ago and I still don't see it here https://groups.google.com/forum/?fromgroups#!forum/mongodb-user
[14:28:04] <Derick> bartzy: changed... quite a few things. Without going into much detail, we handle longer-down nodes better now. And do a lot better with replicaset member failover
[15:21:30] <kali> spuz: the only thing is... when you store lots of small values, keeping the names short can make a difference
[15:21:46] <spuz> kali: yeah I just found some documentation that
[15:22:14] <kali> spuz: in some parts of my dbs, i use one-letter or two-letter field names
[16:38:04] <jimbishop> is there any way to see where you are when you're running a db.copyDatabase() ?
[16:38:59] <jimbishop> i've got a 25G mongo db that i'm trying to copy, and the actual files finished copying almost 2 hours ago. the indexing seems to be going and going with no way to reference where i am in the process.
[20:23:15] <leifw> you should look at ScopedDbConnection
[20:40:29] <mustmodify> I'm manning the free Rails hotline... someone called asking for help with their server config. I've gotten them past some ruby and apache related issues and now I'm getting a mongo error. Hopefully someone can help me.
[20:40:36] <mustmodify> "Could not connect to a master node."
[20:40:41] <mustmodify> so presumably it isn't started?
[20:41:21] <wieshka> Is it possible to setup normal Replica Set on 2 mongo instances ?
[20:45:35] <mustmodify> so I started mongo and I'm getting this error: "Failed to connect to a master node at 127.0.0.1:27017" ... is that the default port?
[20:49:34] <jp-work> mustmodify: I think that's the default port
[20:49:44] <jp-work> that probably means your server failsd to start
[20:50:01] <jp-work> it does some initialization the first time
[20:50:10] <jp-work> like preallocating files and so
[20:50:35] <jp-work> you need to check the log to see what happened / is happening
[21:01:29] <mustmodify> ok new question... once installed will Mongo automatically start up as a service when the machine is rebooted? Or do I need to do something?
[21:01:57] <mustmodify> Seems like it isn't starting up right now because there isn't enough drive space so they are resizing their machine... just wondering whether they should expect Mongo to work when it restarts.
[21:55:26] <alchimista_> how to change this to mongodb select * from pins where id in (select id from msgs where username='bob')
[21:57:15] <Derick> or, perhaps better, redesign your schema so that you can do it in one query
[21:57:16] <alchimista_> I have a collection name msgs and if i do like this "db.msgs.find({username:'bob'},{id:true})" I have resutl that i want
[21:57:30] <alchimista_> so the first query is this: db.msgs.find({username:'bob'},{id:true})
[21:58:07] <alchimista_> now from this result how i have to do the 2nd query, I mean this part --> select * from pins where id in (...)
[21:59:57] <alchimista_> Derick: I think redesign of the schema in this case is not a good solution for me, but any idea how to query on another schema cosidering the result of the first query
[22:00:24] <Derick> alchimista_: you should always consider aligning your data schema with how you query, insert, update and delete things
[22:00:38] <Derick> I know it's a big shift from RDBMSes, but it is the noSQL qay
[22:18:28] <alchimista_> Derick: actually I am using mongoosejs with nodejs this is what i wrote: https://gist.github.com/anonymous/c4e8567a40125ece7d31 , it is null
[22:19:13] <Derick> sorry, can't help you with NodeJS stuff
[22:45:57] <harenson> alchimista_: alchimista_ maybe you could get better support with node stuff at #col.js
[23:54:10] <brycelane> I have a use case question: when storing objects that represent classes in say python or ruby, do people tend to make collections for each type of object, or attach an id tag when storing them and put them in the same collection?
[23:54:43] <Astral303> does mongos create a lock file like mongod when started via --fork?
[23:55:04] <Astral303> seems like the answer is no