ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

MongoDB safe and fsync Explained

Kristina Chodorow explains the MongoDB safe and fsync options:

safe and fsync are not the same, here’s a rundown of the options:

  • safe => false: do not wait for a db response
  • safe => true: wait for a db response
  • safe => num: wait for that many servers to have the write before returning
  • fsync => true: fsync the write to disk before returning. fsync => true implies safe=>true, but not visa versa.
  • If fsync=>false and safe=>true and the write could be in successfully applied to a mmapped file but not yet written to disk.

Related to MongoDB durability.

Original title and link for this post: MongoDB safe and fsync Explained (published on the NoSQL blog: myNoSQL)

via: http://groups.google.com/group/mongodb-user/msg/36ba2b821c438728