Skip to content

DOCS-249-related: change to write concern glossary entry #348

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 29, 2012
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 5 additions & 8 deletions source/reference/glossary.txt
Original file line number Diff line number Diff line change
Expand Up @@ -366,10 +366,6 @@ Glossary
migration of :term:`chunks <chunk>`. Administrators must disable
the balancer for all maintenance operations on a sharded cluster.

fsync
A system call that flushes all dirty, in-memory pages to disk. MongoDB
calls ``fsync()`` every 60 seconds.

chunk
In the context of a :term:`sharded cluster`, a chunk is a contiguous
range of :term:`shard key` values assigned to a particular :term:`shard`.
Expand Down Expand Up @@ -588,10 +584,11 @@ Glossary
nodes have :term:`eventual consistency`.

write concern
A setting on writes to MongoDB that allows the user to specify,
how the database will handle a write operation before
returning. This often determines how many :term:`replica set`
members should propagate a write before returning.
Specifies whether a write operation has succeeded. Write concern
allows your application to detect insertion errors or unavailable
:program:`mongod` instances. For :term:`replica sets <replica
set>`, you can configure write concern to confirm replication to a
specified number of members.

.. seealso:: :ref:`Write Concern for Replica Sets <replica-set-write-concern>`.

Expand Down