Skip to content

Commit 50f2a68

Browse files
author
Sam Kleinman
committed
DOCS-120 edits to the examples in the replica set configuration setting
1 parent eeeb9ae commit 50f2a68

File tree

2 files changed

+223
-181
lines changed

2 files changed

+223
-181
lines changed

source/core/replication.txt

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -496,11 +496,13 @@ your replica set:
496496
- Consider keeping one or two members of the set in an off-site data
497497
center, but make sure to configure the :ref:`priority
498498
<replica-set-node-priority>` to prevent it from becoming primary.
499-
500-
- Create custom write concerns with
501-
:ref:`replica set tags <replica-set-configuration-tag-sets>` to ensure
502-
data is written to specific members of the replica set or to facilitate
503-
data center awareness.
499+
500+
- Create custom write concerns with :ref:`replica set tags
501+
<replica-set-configuration-tag-sets>` to ensure that applications
502+
can control the threshold for a successful write operation. Use
503+
these write concerns to ensure that operations propagate to specific
504+
data centers or to machines of different functions before returning
505+
successfully.
504506

505507
For more information regarding replica set configuration and
506508
deployments see :doc:`/administration/replica-set-architectures`.

0 commit comments

Comments
 (0)