Reputation
4,676
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
7 26
Newest
 Caucus
Impact
~148k people reached

1d
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
Jul
21
revised Backup with mongoexport or mongodump?
deleted 1 character in body
Jul
21
answered MongoDB: dbclient_rs replSetGetStatus failed{ ok: 0.0, errmsg: “unauthorized” }
Jul
21
answered Backup with mongoexport or mongodump?
Jul
13
comment Why does MongoDB extend FileSize if it is already 5x larger than DataSize
You are basically seeing poor re-use (I wrote the SO answer linked above). There are several reasons why it can happen - the free list can become poisoned (rare), or new data doesn't fit in the free space, or you may be hitting the timeout on the free list search which defaults to allocate new space rather than slow things down. You should look at the power of 2 sizes option as mentioned, you can schedule repairs/resyncs every few weeks to reclaim space, or you can look at the newer versions and storage engines for better disk space utilisation in general
May
10
awarded  Nice Answer
Apr
14
answered MongoDB installation Ubuntu 12.04 LTS errors
Mar
31
awarded  Notable Question
Feb
19
awarded  Popular Question
Feb
18
comment Can we resize a already capped collection in mongo db
convertToCapped clones the data to a new collection, drops the old one, see: stackoverflow.com/a/11256419/1148648
Feb
18
comment Can we resize a already capped collection in mongo db
It's not possible at all - what you have done is used the command to convert a non-capped collection to capped. That does not resize an existing capped collection, because resizing a capped collection is simply not possible at present (with or without down time). You can only create new, drop old and copy data between (with mongodump, javascript etc.)