add arb/pv references

Author: kay-kim

source/administration/production-checklist-development.txt

@@ -71,6 +71,10 @@ Replication
      proceed successfully. If you have an even number of members, use
      an :term:`arbiter` to ensure an odd number of votes.
 
+     .. note::
+
+        .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
    - Ensure that your secondaries remain up-to-date by using
      :doc:`monitoring tools </administration/monitoring>` and by
      specifying appropriate :doc:`write concern

source/core/replica-set-architecture-geographically-distributed.txt

@@ -54,6 +54,10 @@ distributions of members include:
   - If Data Center 2 goes down, the replica set remains writeable as
     the members in Data Center 1 can hold an election.
 
+  .. note::
+
+     .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 - Three data centers: one members to Data Center 1, one member to Data
   Center 2, and one member to Data Center 3.
 

source/core/replica-set-architecture-three-members.txt

@@ -61,6 +61,10 @@ provides only one complete copy of the data. Arbiters require fewer
 resources, at the expense of more limited redundancy and fault
 tolerance.
 
+.. note::
+
+   .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 However, a deployment with a primary, secondary, and an arbiter
 ensures that a replica set remains available if the primary *or* the
 secondary is unavailable. If the primary is unavailable, the replica

source/core/replica-set-architectures.txt

@@ -55,6 +55,8 @@ it may be possible to place an arbiter into environments that you would
 not place other members of the replica set. Consult your security
 policies.
 
+.. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 .. warning:: 
 
    In general, avoid deploying more than one arbiter per replica set.

source/includes/steps-deploy-geographically-distributed-replica-set-5member.yaml

@@ -46,6 +46,8 @@ action:
   language: javascript
   code: |
     rs.addArb("mongodb4.example.net")
+post: |
+   .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
 ---
 title: Optional. Configure the member eligibility for becoming primary.
 stepnum: 7

source/reference/method/rs.add.txt

@@ -56,6 +56,8 @@ If ``mongodb3.example.net`` is an arbiter, use the following form:
 
    rs.add('mongodb3.example.net:27017', true)
 
+.. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 .. _rs-add-member-configuration-document:
 
 Pass a Member Configuration Document to ``rs.add()``

source/reference/method/rs.addArb.txt

@@ -20,3 +20,6 @@ Description
    The :method:`rs.addArb()` method takes the following parameter:
 
    .. include:: /includes/apiargs/method-rs.addArb-param.rst
+
+   .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+

source/reference/replica-configuration.txt

@@ -197,6 +197,8 @@ Replica Set Configuration Fields
       :rsconf:`members[n].arbiterOnly` to ``true``
       for the added member.
 
+      .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
    .. rsconf::  members[n].buildIndexes
 
       *Optional*.

source/tutorial/add-replica-set-arbiter.txt

@@ -27,6 +27,10 @@ server or a monitoring host.
 Considerations
 --------------
 
+.. note::
+
+   .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 An arbiter does not store data, but until the arbiter's :program:`mongod`
 process is added to the replica set, the arbiter will act like any other
 :program:`mongod` process and start up with a set of data files and with a

source/tutorial/convert-secondary-into-arbiter.txt

@@ -29,6 +29,10 @@ tutorial. Both procedures are operationally equivalent:
 
   For this procedure, see :ref:`replica-set-convert-secondary-to-arbiter`.
 
+.. note::
+
+   .. include:: /includes/extracts/arbiters-and-pvs-with-reference.rst
+
 .. _replica-set-convert-secondary-to-arbiter-same-port:
 
 Convert Secondary to Arbiter and Reuse the Port Number