Reputation
4,887
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
9 28
Impact
~157k people reached

Aug
25
answered executing shell (bash) commands from within the mongo client
Aug
15
awarded  Nice Question
Aug
13
awarded  Nice Answer
Aug
13
revised MongoDB: RAM requirements
added 64 characters in body
Aug
12
revised MongoDB: RAM requirements
Updated to reflect changes since original answer
Aug
12
awarded  Notable Question
Aug
10
comment How do I (safely) kill long running operations in MongoDB?
Good point, and it's entirely possible that the blank namespace happens more frequently in newer versions - I originally intended to keep the script up to date, but I have now left MongoDB, so that is unlikely I am afraid. If you submit your updated code (with a note that it applies to later versions) here as an answer I will happily vote you up :)
Aug
4
revised mongodb shard chunk migration 500GB takes 13 days - Is this slow or normal?
added link to feature request for reference
Aug
4
awarded  Constituent
Jul
30
answered mongodb is using most of disk space for journal and not cleaning itself
Jul
28
awarded  Caucus
Jul
24
awarded  Enlightened
Jul
24
awarded  Nice Answer
Jul
23
comment MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
I'll bet the main issue with Jesse support is the switch to systemd - the binaries will work fine, but you may need to sort out your own service
Jul
23
comment MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
I amended my answer - if I still worked at MongoDB I might poke a dev to see what's up, but I think the answer would end up being the same. The only "odd" thing I see in your set up is the use of IPV6 which is not widely used (and certainly was not when 2.4 was current), so that might be a possible cause, but I am just speculating at this point
Jul
23
revised MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
Follow up based on comments
Jul
22
comment MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
It's hard to be sure, because I can't see the thread ID or the corresponding timestamp for mongodump, but it looks to me like those errors are independent of the dump, do you have a keyFile configured correctly for those hosts to talk to each other? The monitor will use the keyFile to auth itself to the other hosts in the set, if it is not identical on all hosts you would get errors like that
Jul
22
comment MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
Also, can you paste the full log line? I am interested to see if this is from the mongodump/restore connection or from something else - the replica set monitor is where I have usually seen that messaging, but that is independent of the dump/restore tools
Jul
22
comment MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
has this ever been a 2.6+ replica set?
Jul
21
revised MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
typo