[16:51:21] <lfamorim> Hello! ["statusTelas", "statusCarta", "statusPagamentos"].forEach(function (key) { db.dataprevUpdate.ensureIndex({key : 1}, {background : true}); }) Why MongoDB create a key named key and not statusTelas or statusCarta?
[18:06:18] <helloworld123> hi all - still a noob mongodb user
[18:06:26] <helloworld123> and looking for help to figure out a page_fault issue
[18:07:27] <helloworld123> we're trying to use MMS mongodb management service to help us out
[18:07:42] <helloworld123> but need an API key to finish the login process (old dev signed up for it)
[18:07:53] <helloworld123> is there a work around for the 2-factor o-auth?
[18:53:34] <rocksfrow> hi, do I need to worry about the order I install _minor_ updates to my mongo instances in a primary/secondary/arbiter cluster?
[18:54:01] <rocksfrow> IE, 2.6.x - > 2.6.y... do I need to update my secondary first and what not?
[18:54:10] <rocksfrow> or is that only major upgrades when that matters?
[18:55:48] <rocksfrow> i need to install mongo updates but I am a new mongo user so want to make sure I am installing my updates properly for my cluster
[18:56:44] <rocksfrow> I have MMS setup, and it's warning me everyday to update :P
[18:57:51] <rocksfrow> I am only one minor release behind... if somebody could help assure my worries about minor updates on a cluster I'd appreciate it much! thanks
[18:58:55] <rocksfrow> whoops, ignore that last message dur
[18:59:30] <rocksfrow> all I find when searching is an old 2.2 -> 2.4 upgrade guide... so I am guessing I am cool to just use yum update for minor updates but hoping somebody can make me feel a little better about that
[18:59:38] <rocksfrow> I am using the cluster for PHP sessions, so it's pretty critical :P
[19:56:37] <rocksfrow> 350 ppl... nobody there can help me? pleease lol
[19:57:06] <rocksfrow> i am hoping to get some confirmation that minor updates... IE, 2.6.x -> 2.6.y are safe to install on primary/secondary in any order
[19:57:17] <rocksfrow> or do I need to install minor updates on secondary first
[21:33:54] <rocksfrow> yeah so since I can't get a reply I went ahead with the updates
[21:34:02] <rocksfrow> indeed my sites went down during the update of the primary
[21:34:24] <rocksfrow> looking at the logs, looks like the arbiter detected the master restart and thought about electing, then the master came back up
[21:35:01] <rocksfrow> so I guess in the future, EVEN for minor updates, I should update the secondary, failover to secondary as master, then update original master and revert master
[21:35:10] <rocksfrow> in order to avoid the 30s of downtime