Write operations that use this write concern will wait for acknowledgement from the primary server before returning.
Write operations that use this write concern will wait for acknowledgement from the primary server before returning. Exceptions are raised for network issues, and server errors.
Exceptions are raised for network issues, and server errors; the write operation waits for the server to group commit to the journal file on disk.
Exceptions are raised for network issues, and server errors; waits on a majority of servers for the write operation.
Write operations that use this write concern will return as soon as the message is written to the socket.
Write operations that use this write concern will return as soon as the message is written to the socket. Exceptions are raised for network issues, but not server errors.
Write operations that use this write concern will wait for acknowledgement from a single member.
Write operations that use this write concern will wait for acknowledgement from two members.
Write operations that use this write concern will wait for acknowledgement from three members.
Tag set named write concern or a "majority" write concern.
Tag set named write concern or a "majority" write concern.
Write Concern tag set name or "majority", representing the servers to ensure write propagation to before acknowledgment. Do not use string representation of integer values for w.
Create a WriteConcern with the set number of acknowledged writes before returning
Create a WriteConcern with the set number of acknowledged writes before returning
number of writes
Controls the acknowledgment of write operations with various options.
w
- 0: Don't wait for acknowledgement from the server - 1: Wait for acknowledgement, but don't wait for secondaries to replicate - >=2: Wait for one or more secondaries to also acknowledge - "majority": Wait for a majority of secondaries to also acknowledge - "<tag set name>": Wait for one or more secondaries to also acknowledge based on a tag set name
wTimeout
- how long to wait for slaves before failing- 0: indefinite - >0: time to wait in milliseconds
Other options:
-
journal
: If true block until write operations have been committed to the journal. Cannot be used in combination withfsync
. Prior to MongoDB 2.6 this option was ignored if the server was running without journaling. Starting with MongoDB 2.6 write operations will fail with an exception if this option is used when the server is running without journaling.Implicit helper
The ScalaWriteConcern implicit allows for chainable building of the WriteConcern eg:
val myWriteConcern = WriteConcern.ACKNOWLEDGED.withJournal(true)).withWTimeout(Duration(10, TimeUnit.MILLISECONDS))
1.0