Skip to content

Update sharded-cluster-high-availability.txt #1479

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

Update sharded-cluster-high-availability.txt #1479

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
2 changes: 1 addition & 1 deletion source/core/sharded-cluster-high-availability.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Application Servers or :program:`mongos` Instances Become Unavailable
If each application server has its own :program:`mongos` instance, other
application servers can continue access the database. Furthermore,
:program:`mongos` instances do not maintain persistent state, and they
can restart and become unavailable without loosing any state or data.
can restart and become unavailable without losing any state or data.
When a :program:`mongos` instance starts, it retrieves a copy of the
:term:`config database` and can begin routing queries.

Expand Down