Skip to content

DOCS-1590: Ensure config servers are accessible to other members of the ... #1213

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
wants to merge 1 commit into from
Closed

DOCS-1590: Ensure config servers are accessible to other members of the ... #1213

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
8 changes: 8 additions & 0 deletions source/tutorial/deploy-shard-cluster.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,14 @@ instances, each running on different servers to assure good uptime and
data safety. In test environments, you can run all three instances on a
single server.

.. note::

Config servers and all other members of a sharded cluster must be visible to
each other across the network. Firewalls and other security configurations
must include rules to allow that access. For example, Amazon Web Services
provides a security group feature that must be configured to provide network
visibility to all members of a sharded cluster.

Config server instances receive relatively little traffic and demand
only a small portion of system resources. Therefore, you can run an
instance on a system that runs other cluster components.
Expand Down