3 ms·
Corruption... as I said, doing db.repair often brought the records back, although it did take my application down for quite some time.
by captaincrunch 16y ago
Corruption... as I said, doing db.repair often brought the records back, although it did take my application down for quite some time.
- stuff4ben 16y agoare you sure you don't have a HD/controller going bad? From what it sounds like no one has this problem and you haven't given steps to reproduce it.
- captaincrunch 16y agoRackspace Cloud support is telling me the hardware we are running on checks out 100%.
- spuz 16y agoReading the documentation about durability and repair[1], it appears data corruption should only ever occur if you had a hardware failure, or the mongodb process crashed or was killed. Was the data corruption you experienced because of any of these reasons? In your experience, how easy is it to repair a node vs switch to a replica node and rsynch. (I'm quite ignorant about MongoDB replication but in my idealised mind, it should be possible to recover a corrupted node entirely automatically and transparently to the client). [1]http://www.mongodb.org/display/DOCS/Durability+and+Repair http://www.mongodb.org/display/DOCS/Durability+and+Repair