content_image/754783.jpg content_image/754784.jpg
Changed in version 2.6: Specifying a write concern that includes j: true to a mongod or mongos running with --nojournal option now errors. Previous versions would ignore the j: true . 

Note: Requiring journaled write concern in a replica set only requires a journal commit of the write operation to the primary of the set regardless of the level of replica acknowledged write concern. 

wtimeout This option specifies a time limit, in milliseconds, for the write concern. wtimeout is only applicable for w values greater than 1 . 

wtimeout causes write operations to return with an error after the specified limit, even if the required write concern will eventually succeed. When these write operations return, MongoDB does not undo successful data modifications performed before the write concern exceeded the wtimeout time limit. 

If you do not specify the wtimeout option and the level of write concern is unachievable, the write operation will block indefinitely. Specifying a wtimeout value of 0 is equivalent to a write concern without the wtimeout option. 

## See also: 

Write Concern Introduction (page 78) and Write Concern for Replica Sets (page 80). 

## SQL to MongoDB Mapping Chart 

In addition to the charts that follow, you might want to consider the Frequently Asked Questions (page 743) section for a selection of common questions about MongoDB. 

## Terminology and Concepts 

The following table presents the various SQL terminology and concepts and the corresponding MongoDB terminology and concepts. 

<img src='content_image/754783.jpg'>

## Executables 

The following table presents some database executables and the corresponding MongoDB executables. This table is not meant to be exhaustive. 

<img src='content_image/754784.jpg'>

