[03:16:48] <regreddit> we use replicas, so I can't see this happening, but i'm putting the index commands into my server's startup, and want to see if they need to be built or rebuilt ever
[05:30:11] <pootietang> I'm having a problem running mongodb on opensuse. I get the following error: JavaScript execution failed: Error: couldn't connect to server 127.0.0.1:27017 at src/mongo/shell/mongo.js:L112
[05:31:29] <pootietang> any tip would be appreciated
[08:19:19] <dtrott> If I have a (Java) object that has its own custom serialization (byte [] about 4k) whats the best way to store that in Mongo ? I can create a wrapper DBObject with a single data field but that seems somewhat redundant since I don't really need a wrapper with just one field ? PS Also using Spring Data if that helps..
[09:03:37] <goog> "The minimum recommended number of slave servers are 3." <--- why 3? 1 master + 3 slaves?
[09:26:07] <Nodex> are you confusing slaves with replicas?
[10:02:29] <goog> Nodex: maybe. is slave different than secondary of replica set?
[10:03:31] <crashev> Derick: hello, just to make sure, isnt there other way in order to upgrade mongodb from 1.4.x to 2.2.x than the path 1.6, then 1.8, then 2.0, then 2.2, isnt there something like just dumping data, doing upgrade to 2.2.x and then reloading data like in relational sql data bases?
[10:21:47] <theblackbox> hello all, I'm struggling with starting the mongod process as a service that is then disowned - it currently locks up the shell instance that calls it and so stalls my deployment script. Any suggestions?
[10:35:14] <theblackbox> sorry, got called into a meeting
[10:35:33] <HarryT> Could somebody tell me how I can update my questions object? If a value isn't there, it needs to be added. If a value is there, it needs to be updated. This is the json equivelent of my object - http://pastebin.com/G47GfZ2w
[10:35:40] <HarryT> Any help would be greatly appreciated!
[10:39:08] <Derick> crashev: hmm, it is something to try
[10:39:48] <Derick> crashev: I suggest you: 1. shut down mongod. 2. make a backup of the data files. 3. start MongoDB 2.4 and see whether it works first
[11:29:55] <crashev> Derick: ok,I will try that as well, but how about doing 1.dump of data like mysqldump or pg_dumpall, 2. shutdown current mongodb 1.4, 3. upgrade to 2.x (clean install), 4. restoring data in 2.2 from dump made using mongodb 1.4 -> is this possible, or this logic does not apply here to mongodb ?
[11:38:14] <Derick> crashev: you can try that too - don't go to 2.2 though, upgrade to 2.4!
[11:38:41] <Derick> crashev: I think dump and restore is just going to be slower
[11:41:32] <crashev> Derick: ok, will upgrade to 2.4 then
[11:41:36] <Derick> crashev: do not forget a backup
[11:55:19] <Garo_> I have a strange problem: My 300GB database is doing around 650 queries per second and around 200 updates per second. For some reason the database reads over 8000 i/o operations per second from the SSD storage, that's over 200MB (megabytes) per second. I can't find any logical reason why it's doing so much reads. Any ideas? All my slaves (two) are in sync. mongostat reports around 300 page faults per second. the documents ...
[11:55:25] <Garo_> ... are quite small, around few kilobyte per document
[13:00:57] <NoReflex> hello! I'm trying to find average and sum for some fields in a mongo collection; all the example I've seen mentioned using a group clause but I don't need to group anything
[13:01:14] <NoReflex> so far the only solution for me is to use $group but use null fro _id
[13:44:42] <jeanre> I'm getting can't append to array using string field name: comments
[13:45:04] <jeanre> there is an array of pages which contain an array of comments
[14:06:12] <HarryT> Could somebody tell me how I can update my questions object? If a value isn't there, it needs to be added. If a value is there, it needs to be updated. This is the json equivelent of my object - http://pastebin.com/G47GfZ2w
[14:16:12] <NoReflex> take a look at upsert http://docs.mongodb.org/manual/reference/method/db.collection.update/
[14:24:56] <HarryJT> I tried doing an update with upsert and it still removed the previous values though?
[14:25:06] <HarryJT> I'll try again in about 15 minutes, gotta do a windows reinstall on a machine first!
[14:49:21] <grexican> Hey Derick. You were helping me yesterday with a $match issue where I was trying to match on subdocuments and filter them out of a subdocument. I came up with a solution using a bit of rolling and unrolling and using $eq like you suggested. I can pastie it if you're interested in seeing it. And of course no hard feelings if you couldn't care less to see it :)
[18:51:22] <cheeser> if you look at MapperOptions, there's a setStoreEmpties()
[18:51:30] <cheeser> and setStoreNulls() for that matter.
[18:51:55] <cheeser> set up your MapperOptions how you'd like and create a Mapper with those options then pass that Mapper to Morphia when you create it.
[18:53:29] <patricioe> awesome. Will look into that. Thanks.
[20:07:23] <patricioe> :cheesed I tried your suggestion and still I'm not able to store an empty array. Any other suggestion ?
[20:07:50] <patricioe> I have debugged the code a bit and I see the options properly set right before calling the DAO.save().
[20:08:19] <patricioe> after that, the database still shows null in the field that should contain an empty array.
[20:13:08] <gswain> I'm not sure if i can ask questions related to the php driver here: but I have a collection names schools and each document has an numerically indexed array called zips. i want to find all schools that have the zip code '83757' in their zip code array. I see examples for querying associative arrays but not for arrays where you don't know the index you are looking for
[20:13:25] <patricioe> :cheeser (sorry I keep misspelling your name)
[21:48:12] <pasichnyk> hey guys, i'm just rolling out a mongodb deployment (3 node replicaset) and when i have a decent volumes of writes ($inc/upsert's) cpu pegs at 100% and set becomes unresoponve off and on, resulting in growing replication lag. Is the only way to get around this to change my write patterns and/or shard, or are there settings that would impact this behavior in a positive way?
[21:50:09] <pasichnyk> If i completely stop the update calls, it will recover around 1000s of replication lag very quickly, say less than a minute. just seems odd that it lags so hard if the PRIMARY can continue to handle the write patterns...
[21:52:35] <ruphos> your document schema can have an effect. I've experienced significant issues with having subdocument arrays that were growing often, as the bson data has to get grown and shifted around
[21:53:21] <kali> http://docs.mongodb.org/manual/reference/command/collMod/#usePowerOf2Sizes can help when documents are growing
[21:53:26] <pasichnyk> my documents do need to grow a bit, as the data going into them isn't known ahead of time, but most of the updates are just $inc of existing elements. I did set powerOfTwo sizes already
[21:53:48] <ruphos> what is your "decent volume" of writes?
[21:55:58] <pasichnyk> i was processing from a queue, and it was saying between 50 and 100 items processed/sec. Each item is a single document update, that runs $inc operations on 1..n values in document. (where n could be in the 100's, but probably more like double digits)
[21:57:52] <pasichnyk> i just double checked collections, and the stats reports "userFlags" : 1, so it looks like powerOf2Sizes is enabled.
[22:01:58] <pasichnyk> ruphos, i don't have subdocument arrays, i do have a level or two of schema though, following the pattern recommended in the blog about how mms is built. keeping track of data at say a hourly and daily level in a single document.
[22:04:44] <ruphos> I'm not sure then. The subdocs were the majority issue that I've experienced. Other than that, I've only run into replication issues when migrating between collections and doing 30k+ inserts/sec. Which definitely does not seem to be applicable.
[22:05:01] <pasichnyk> most of my schemas though (18 of 22 collections) have a schema more like this: http://pastebin.com/BHeRh36T
[22:05:42] <pasichnyk> yeah, these boxes have raid10 ssd storage, and also WAY more memory that dataset currently...
[22:06:25] <pasichnyk> the query for my update specifies the _id value (indexed) as well as the full metadata node (also indexed now), so that it can create the schema if its not alredy there.
[22:06:38] <pasichnyk> anything seem alarming there, or that pretty standard?
[22:25:54] <pasichnyk> np, thanks for the thoughts. Maybe someone else has a silver bullet. :)
[22:36:34] <pasichnyk> how's this for a 'locked db' output from mongostat: summaries:1853.7% (that makes no sense, right?)
[22:44:45] <DrStein> Hi. Is it possible to change all 3 config servers' hostnames in one operation?
[22:45:10] <DrStein> I used the actual hostnames and I'd like to start using CNAMEs instead.
[22:48:07] <pasichnyk> hrm, this looks odd. I see that when the cpu i spiked on a box, in db.currentOp() i see "serverStatus":1 running, for over 2 minutes. That should be an instant query right?
[22:48:26] <pasichnyk> I'm guessing its from my mms agent