3,416 reputation
317
bio website comerford.cc
location Ireland
age 35
visits member for 2 years, 7 months
seen 5 hours ago

I currently work for MongoDB, Inc. and have a background in operations, networking and system administration. You can find me in all the usual places, but probably the most useful and relevant are listed below:

Personal Site/Blog
LinkedIn
Twitter
Stack Overflow Careers


Sep
13
comment Understanding two types of mongodb log entries for bulk inserts
As Asya mentioned in the other posted question on this topic, this is not a simple Q&A type of problem and requires detailed troubleshooting to be anything besides guess work. Please post your question in the mongodb-user google group but be aware that this type of issue will not usually be solved straight away and will require significant information gathering, some of which Asya mentioned already
Sep
11
comment Long running query on replica worker set in mongo
That's because something/someone has sent the killOp command for that operation (not advised)
Sep
11
answered Long running query on replica worker set in mongo
Sep
11
revised Long running query on replica worker set in mongo
added 102 characters in body; edited title
Sep
11
awarded  Tag Editor
Sep
11
revised sharding wiki excerpt
added 424 characters in body
Sep
11
revised sharding wiki description
added 924 characters in body
Sep
11
wiki created sharding description
Sep
11
wiki created sharding excerpt
Sep
11
suggested suggested edit on sharding tag wiki
Sep
11
suggested suggested edit on sharding tag wiki excerpt
Sep
11
awarded  Taxonomist
Sep
8
comment MongoDB ReplicaSet reconfig when primary and majority don't exist
There is an example of the .Net command document here: groups.google.com/forum/#!msg/mongodb-user/OkU59UWAsCY/… and you should be able to pass in the force:true at that point. Similarly, you may need to set slaveOK or equivalent to get it to work (collectionSettings.SlaveOk = true) - sorry, .NET is not my thing. If you can't figure it out, then a quick question on StackOverflow with .NET and MongoDB tags should get it sorted for you pretty quickly :)
Sep
6
answered MongoDB ReplicaSet reconfig when primary and majority don't exist
Sep
4
comment Sharded DB accidentally created during update of MongoDB from 2.4.4 to 2.6.4
It's not advised to run mixed major versions for an extended period at all - creating a sharded DB might work, but you may also hit unexpected problems. The secondaries not being up to date makes the entire thing more risky - that would be my first priority - getting a secondary up to date, then proceed as advised. Secondaries should not take so long to catch up, even with large data sets - sounds like that set might be struggling in general, though that is beyond the scope of these comments really
Sep
4
comment Sharded DB accidentally created during update of MongoDB from 2.4.4 to 2.6.4
Yes, though I would recommend stepping the 2.4 node down to secondary first, then turning on the balancer. The primaries do all the real work for migrations (coordinated by the balancer), so stepping one down while the balancer is active can cause aborted migrations and orphaned documents. Neither of those things is a huge problem (in fact you probably won't notice) but I would generally avoid them if possible.
Sep
3
answered Sharded DB accidentally created during update of MongoDB from 2.4.4 to 2.6.4
Aug
6
revised How we can take backup oplog on every hour and apply on top on full backup for mongodb
added 79 characters in body
Aug
6
answered How we can take backup oplog on every hour and apply on top on full backup for mongodb
Jul
31
comment mongodb import … taking very long time
Also the backtick at the start of the SEQ fieldname is a bit odd but it works in my testing - I'm wondering if the version you are using is not so forgiving.