Skip to content

update production-checklist-operations.txt #2246

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 production-checklist-operations.txt #2246

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
6 changes: 3 additions & 3 deletions source/administration/production-checklist-operations.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,13 +47,13 @@ Replication
downtime windows to avoid the need for a full resync.

- The replication oplog window should cover the time needed to
restore a replica set member, either by an initial sync, or
restore a replica set member, either by an initial sync or
restoring from the last backup.

- Ensure that your replica set includes at least three data-bearing nodes
with ``w:majority`` :doc:`write concern
</reference/write-concern>`. Three data-bearing nodes are
required for replica set wide data durability.
required for the replica set wide data durability.

- Use hostnames when configuring replica set members, rather than IP
addresses.
Expand All @@ -79,7 +79,7 @@ Sharding

.. cssclass:: checklist

- Pplace your :doc:`config servers
- Place your :doc:`config servers
</core/sharded-cluster-config-servers>` on dedicated hardware for
optimal performance in large clusters. Ensure that the hardware has
enough RAM to hold the data files entirely in memory and that it
Expand Down