Skip to content
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.

Sign up for GitHub

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

Jump to bottom

minor typographical #2832

Closed
wants to merge 1 commit into from
Closed

minor typographical #2832

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/faq/concurrency.txt
View file
Open in desktop
Expand Up @@ -31,7 +31,7 @@ What type of locking does MongoDB use?
In addition to a shared (S) locking mode for reads and an exclusive
(X) locking mode for write operations, intent shared (IS) and intent
exclusive (IX) modes indicate an intent to read or write a resource
using a finer granularity lock. When locking at a certain granularity
using a finer granularity lock. When locking at a certain granularity,
all higher levels are locked using an :term:`intent lock`.

For example, when locking a collection for writing (using mode X),
Expand Down Expand Up @@ -172,7 +172,7 @@ of a :term:`replica set`, take the :program:`mongod` offline and let
other members of the set service load while maintenance is in progress.

The following administrative operations require an exclusive
(i.e. write) lock on the database for extended periods:
lock at the database level for extended periods:

- :method:`db.collection.createIndex()`, when issued
*without* setting ``background`` to ``true``,
Expand Down Expand Up @@ -312,11 +312,11 @@ Can reads see changes that have not been committed to disk?

.. versionchanged:: 3.2

MongoDB 3.2 introduces :ref:`3.2-rel-notes-readConcern` option.
MongoDB 3.2 introduced the :ref:`3.2-rel-notes-readConcern` option.
Clients using :readconcern:`majority` ``readConcern`` cannot see the
results of writes before they are made :term:`durable`.

Readers, using :readconcern:`"local"` ``readConcern`` can see the
Readers using :readconcern:`"local"` ``readConcern`` can see the
results of writes before they are made :term:`durable`, regardless of
write concern level or journaling configuration. As a result,
applications may observe the following behaviors:
Expand Down