Timeline for mongodb config servers not in sync
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2017 at 19:24 | comment | added | Adam C | If you have an urgent issue I would recommend getting professional advice on this - contact MongoDB and ask them for support. I no longer work for MongoDB and would not feel to talk you through this kind of procedure, particularly for more recent versions of the database where this kind of issue has changed substantially (this answer was written almost 4 years ago) | |
| Apr 29, 2017 at 3:31 | comment | added | rendybjunior | hi AdamC, I am currently having the same problem and it is very urgent for me to do it as soon as possible. I have a quick question. Do I have to stop all mongos and mongod before shutdown the configdb? | |
| Jun 30, 2016 at 7:22 | comment | added | Amit Tripathi | I followed what you said I only see the "md5" : "d41d8cd98f00b204e9800998ecf8429e"of 3 config server as same. How do i correct the error? | |
| Sep 1, 2015 at 17:51 | comment | added | snetch | For the second category, I don't see a "databases" collection. How important is it if other things like "chunks" are in sync? Can it be found elsewhere? | |
| Aug 19, 2013 at 16:56 | history | answered | Adam C | CC BY-SA 3.0 |