Skip to content

DOCS-297 migrated distributed locking info to manual #296

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 4 commits into from
Oct 9, 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
7 changes: 6 additions & 1 deletion source/core/sharding-internals.txt
Original file line number Diff line number Diff line change
Expand Up @@ -348,10 +348,15 @@ The migration process ensures consistency and maximizes availability
of chunks during balancing: when MongoDB begins migrating a chunk, the
database begins copying the data to the new server and tracks incoming
write operations. After migrating chunks, the "from" :program:`mongod`
sends all new writes, to the "receiving" server. Finally,
sends all new writes to the "receiving" server. Finally,
:program:`mongos` updates the chunk record in the :term:`config
database` to reflect the new location of the chunk.

.. note:: Before MongoDB version 2.0, increasing clock skew between
:program:`mongos` instances could lead to failed distributed locks
and potential data loss, particularly if the skew exceeded 5 minutes.
Always run ``ntpd`` to minimize clock skew.

.. _sharding-migration-thresholds:

Migration Thresholds
Expand Down