Skip to content

DOCS-378 added note on idempotency of oplogs #138

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

Merged
merged 1 commit into from
Aug 20, 2012
Merged

DOCS-378 added note on idempotency of oplogs #138

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions source/core/replication-internals.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,16 @@ exceptional situations may cause secondaries to lag behind further. See
All members send heartbeats (pings) to all other members in the set and can
import operations to the local oplog from any other member in the set.

Replica set oplog operations are :term:`idempotent`. Idempotency is
required because of the following operations:

- initial sync
- post-rollback catch-up
- sharding chunk migrations


.. TODO. Verify that "sharding chunk migrations" (above) requires idempotency

For more information about the oplog, see :ref:`oplog sizing <replica-set-oplog-sizing>`.

.. In 2.0, replicas would import entries from the member lowest
Expand Down