3 ms·
MongoDB has been durable for a while with journalling. They're only just enabled safe mode (i.e. synchronous) for the clients by default, but this is something
by ukd1 14y ago
MongoDB has been durable for a while with journalling. They're only just enabled safe mode (i.e. synchronous) for the clients by default, but this is something different to being durable.
If you want a durable write; you should not disable journalling and use safe mode / getlasterror with the desired writeconcern setting - http://docs.mongodb.org/manual/reference/command/getLastError/#getLastError http://docs.mongodb.org/manual/reference/command/getLastErro...
- taligent 14y ago> If you want a durable write; you should not disable journalling and use safe mode / getlasterror with the desired writeconcern setting Sure. Which is the default approach of almost all of the drivers.
- ukd1 14y agoNot quite true; historically most (i.e. official) defaulted to safe=false. Also safe=true only makes sure the server acknowledged your write; writeconcern allows you to wait for it to be written to the journal or more. Also, journalling is not controllable via client drivers, only via startup flags / config options.