[12:18:13] <tscanausa> Ephexeve: it depends. I have no direct experience with either but some times the mongodb ones are not so great. I would recommend trying them out.
[12:26:51] <jordana> Thoughts on the need for RAID1 on shards if they're setup as 3+ replic sets?
[12:27:26] <tscanausa> jordana: I personally dont think it is needed.
[12:27:33] <jordana> tscanausa: that's what I'm thinking.
[12:27:44] <jordana> tscanausa, by the way, the sync finished successfully this morning :)
[12:28:10] <tscanausa> jordana: hah awesome, what was wrong?
[12:28:17] <tscanausa> are you cloud or dedicated?
[12:51:07] <Strekerud> Hi! Is there anyone with experience with MongoSessionManager who has some spare time to help me out?
[12:54:10] <Strekerud> I'm trying to persist web forms using MongoSessionManager. Persistence of the same page works with JDBCSessionManager, but it's way too slow. The sessions stored in the mongodb doesn't seem to update at all as I click through the form, nor does it persist during failover.
[12:59:47] <Tajt> if I run db.dropdatabase on a mongodb and then recreate it from a previous dump, giving it the same name, is there any risk of old data laying around still or is everything guaranteed to be removed even if I do not run any repair command?
[13:00:53] <tscanausa> Tajt: technically you should be good but there is a race condition if you do it too fast
[13:37:44] <Strekerud> Anyone with any experience using MongoSessionManager?
[14:00:04] <Diplomat> Hey guys! Any ideas why I can't use "FindOne" method here's what I have http://pastebin.com/pmu3Ac2y (error and code that creates it)
[14:00:46] <Diplomat> and this "using" list is what I'm using
[14:01:29] <Diplomat> I'm following this info here: http://docs.mongodb.org/ecosystem/tutorial/getting-started-with-csharp-driver/
[14:17:25] <blarghmatey> Does anyone happen to know what the output of rs.status or rs.config are while a replica set is still initializing?
[14:17:46] <blarghmatey> I need to know so that I can add some flow control into a script to prevent performing writes during initialization.
[16:02:06] <postitnote> Anyone here using macports mongodb on osx mavericks?
[16:44:56] <postitnote> can I just chmod everything 777? We're all adults here.
[16:45:47] <postitnote> What would one enable permissions on to fix this problem?
[16:56:44] <ianblenke> I'm having a difficult time re-establishing a replication set on a new mongo cluster that is a restore from a production mongo cluster
[16:58:37] <ianblenke> I've removed the replSet argument, done a "use local" and "db.dropDatabase()" while in stand-alone mode, "use admin" followed by "db.shutdownServer()" then restarted mongo with the replSet argument and did an rs.initiate() with the json arguments of that node.
[16:59:23] <ianblenke> it looks like a healthy master. but when I try to add an empty mongo server running with the same replSet, it just keeps saying "replSet can't get local.system.replset config from self or any seed (EMPTYCONFIG)" and the master doesn't seem able to do an rs.add() on it.
[17:12:20] <freeone3000> ianblenke: Does it have the same replSet in its config? Do you use authentication?
[20:06:09] <dgarstang> I need some help with mongo credentials. Is there a better doc than this? http://docs.mongodb.org/manual/tutorial/enable-authentication/ ?
[20:06:30] <dgarstang> because, if you follow that, and then authenticate as that user, you cant' even to a sh.status()
[20:07:43] <dgarstang> Specifically a sh.status() returns "not authorized for query on config.version"
[20:08:12] <dgarstang> Those docs are pretty ... slim. So, the admin user isn't really an admin user as defined by that doc?
[20:09:34] <dgarstang> and the guys that are trying to use this are saying "de (unable to review cluster state, insert something, review config db, etc.).." ... no auth for those. So, the admin user, as defined by that doc, apparently can't do any db operations
[20:13:07] <BlueDo> Is anyone able to get Mongo working with XAMPP?
[20:15:14] <dgarstang> omg mongo. why do I have to write a damn json blob to run a command?
[20:16:59] <tjbiddle> Hey all - I'm trying to configure a hidden replica set member; however I'm not overly experienced in mongo. I'm looking at http://docs.mongodb.org/manual/tutorial/configure-a-hidden-replica-set-member/ and it doesn't explain what file I need to be editing
[20:28:35] <Almindor> hey, does mongodb have a bug between mongoexport and mongoimport when date is ISODate("1970-01-01T00:00:00Z") ?
[20:28:52] <Almindor> it's giving me error BSON representation of supplied JSON is too large: code BadValue: BadValue: Year out of range: 1969
[20:29:12] <Almindor> note: same mongodb version (2.6.1) with the data being just piped from mongoexport to mongoimport
[20:29:37] <Almindor> also if I put that isodate in a variable and do .getYear() it gives me 1969, which I guess is what's the problem here (local vs iso?)
[20:36:27] <decompiled> Has anyone seen a lot of splitvector queries that take a long time (30+ mins) on a sharded cluster?
[20:39:38] <cheeser> yes. let me try to remember the reasoning...
[20:55:12] <kamoricks> I would like to add a member to a replica set that will never become primary, doesn't vote, and is only hit by queries when specifically mentioned. What is the word for this?
[20:55:21] <loincloth> hey all... is anyone here familiar with the Mongoid library for Ruby?
[20:56:26] <loincloth> or the official MongoDB Ruby driver?
[21:03:22] <loincloth> kali: sure, i was just treading lightly because i wasn't sure it would be on topic
[21:03:35] <loincloth> i am unclear about how some caching is working out
[21:03:52] <loincloth> in a test environment, i wanted to track when embedded documents were created
[21:04:15] <loincloth> so i had something like: criteria = user.rankings.some_scope
[21:04:31] <loincloth> and then i would do assertions against things like criteria.count and criteria.last's attributes
[21:04:51] <loincloth> this worked up until i expected those value to change and i struggled for a while until i eventually just repeated the expression i used to assign criteria to begin with
[21:04:59] <loincloth> after the point it should have changed
[21:05:15] <loincloth> and then i was getting expected results, whereas the criteria variable object was still returning cached results
[21:06:31] <loincloth> i've started looking into it and it's not clear right away who is responsible for this(mongoid? moped? mongodb ruby driver? mongodb itself?) so i was hoping to take a shortcut via some helpful humans
[21:07:19] <loincloth> even a tip about who is responsible would be helpful and i get look into the details
[21:15:11] <kali> loincloth: i think this is in mongoid scope
[21:16:19] <kali> loincloth: mongodb ruby driver does not do anything like that, but as far as i know, mongoid no longer uses it
[21:16:29] <kali> loincloth: depending on your mongoi version of course
[21:18:16] <kali> loincloth: unfortunately, mongoid is huge and complex contraption.
[21:19:43] <kali> loincloth: http://rdoc.info/github/mongoid/mongoid/Mongoid/QueryCache maybe this can be a relevant starting point
[21:25:02] <loincloth> kali: my hunch is you are right about the scope, but i'm not clear on some of the rest there... like http://mongoid.org/en/mongoid/docs/extras.html#caching suggests the official ruby driver is still in play
[21:25:08] <loincloth> but the docs could of course be out of date
[21:30:02] <loincloth> i might be able to go to 4... i didn't really realize 4 even existed... i installed mongoid without a version requirement to start and then locked it to the one i got which was 3.0.23... at least i think that's what happened now i dunno anything anymore :P
[21:30:22] <kali> loincloth: honestly, don't rush into this :)
[21:30:47] <loincloth> oh i'm not gonna was just thinking that i have no hard requirement to be on 3.x that i'm aware of
[21:31:01] <loincloth> but i realize my rambling is complicating the train of thought here, sorry :P
[21:32:47] <kali> loincloth: check what cache? do on your criteria maybe
[21:35:30] <loincloth> kali: heh... well... what i am seeing is criteria.cached? returns false always and differs from the value of repeating the expression which created criteria
[21:36:55] <loincloth> kali: yeah... fwiw glancing at the source for 3.0.23 does seem to suggest the official driver is no longer in play which seems noteworthy
[21:37:15] <loincloth> i was vaguely aware of that, i would say, and just read that extras section and assumed it knew what it was talking about... oops
[21:37:24] <loincloth> but i had seen various references to Moped already of course
[21:37:25] <kali> loincloth: yeah, i was pretty sure of this because this was the reason why we stayed on 2.x
[21:37:48] <loincloth> mmkay... guess i'll dig around with Moped for a little while
[21:38:39] <kali> yeah. if you want to convince you that the server side is not behaving badly (i'm convinced here) you can run a mongosniff or set the profiler at level 2
[21:39:36] <kali> maybe the log can tell you that too... but the log will be generated by moped too
[21:47:00] <loincloth> kali: thx a lot for the help and effort
[21:57:34] <loincloth> kali: btw, do you have a preference for alternative to mongoid?
[21:58:20] <loincloth> i was following lead of a team member who i don't think has a ton of experience to the point of necessarily demanding mongoid... i have even less so no opinions yet other than creeping issues with mongoid not behaving as expected and difficulty understanding why
[21:59:04] <loincloth> i don't have a strong sense of what the Ruby community at large uses, etc.
[21:59:41] <kali> loincloth: i am not a big fan, as you have guessed, but i haven't had a chance to try anything else. i think it's probably the "safe" choice, as in "most projects will use it"
[22:01:10] <loincloth> kali: cool, thx again, i'm out the door... have a good one
[22:14:38] <freeone3000> I would like to add a member to a replica set that will never become primary, doesn't vote, and is only hit by queries when specifically mentioned. What is the word for this?
[22:15:24] <freeone3000> Non-voting arbiter doesn't make sense because it doesn't hold data. priority-zero non-voting members still get hit by queries.