Skip to content

DOCS-2474: mirrored mongod must be within 30 secs #2613

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

Closed
ravindk89 wants to merge 1 commit into from
Closed

DOCS-2474: mirrored mongod must be within 30 secs #2613

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
12 changes: 9 additions & 3 deletions source/core/sharded-cluster-config-servers.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,15 @@ Replica Set Config Servers
.. include:: /includes/fact-config-server-replica-set-restrictions.rst

Earlier versions of MongoDB required *exactly three* mirrored
:program:`mongod` instances to act as the config servers. MongoDB 3.2
deprecates the use of three mirrored :program:`mongod` instances for
config servers.
:program:`mongod` instances to act as the config servers. If you are using
*mirrored* config servers, each server's system clock must be within 30
seconds of each other server for the distributed lock manager to work
properly. With *mirrored* config servers, minimize clock skew by running the
network time protocol (NTP) ``ntpd`` on your servers. MongoDB 3.2 deprecates
the use of three mirrored :program:`mongod` instances for config servers.

With replica set config servers, clock skew does not affect distributed lock
management.

Each sharded cluster must have its own config servers. Do not use the
same config servers for different sharded clusters.
Expand Down