diff --git a/source/administration/replica-sets.txt b/source/administration/replica-sets.txt index b036ab07932..eebb99814e2 100644 --- a/source/administration/replica-sets.txt +++ b/source/administration/replica-sets.txt @@ -21,11 +21,15 @@ suggestions for administers of replica sets. The following tutorials provide task-oriented instructions for specific administrative tasks related to replica set operation. +.. Updates to this tutorial list should also be made in + source/replication.txt + - :doc:`/tutorial/deploy-replica-set` + - :doc:`/tutorial/convert-standalone-to-replica-set` - :doc:`/tutorial/expand-replica-set` - :doc:`/tutorial/deploy-geographically-distributed-replica-set` - :doc:`/tutorial/change-oplog-size` - - :doc:`/tutorial/convert-replica-set-to-replicated-shard-cluster` + - :doc:`/tutorial/force-member-to-be-primary` - :doc:`/tutorial/change-hostnames-in-a-replica-set` - :doc:`/tutorial/convert-secondary-into-arbiter` @@ -333,9 +337,9 @@ the event of a network partition. Procedures ---------- -For procedures on deploying replica sets, see the -:doc:`/administration/replication-architectures` document and the -:ref:`list of replica set tutorials `. +This section gives overview information on certain procedures. Most +procedures, however, are found in the :ref:`replica set tutorials +`. .. _replica-set-admin-procedure-add-member: diff --git a/source/replication.txt b/source/replication.txt index e4b33043c5e..f84cff74ac4 100644 --- a/source/replication.txt +++ b/source/replication.txt @@ -38,6 +38,9 @@ Tutorials The following tutorials describe certain replica set maintenance operations in detail: +.. Updates to this tutorial list should also be made in + source/administration/replica-sets.txt + .. toctree:: :maxdepth: 1 @@ -46,6 +49,7 @@ operations in detail: tutorial/expand-replica-set tutorial/deploy-geographically-distributed-replica-set tutorial/change-oplog-size + tutorial/force-member-to-be-primary` tutorial/change-hostnames-in-a-replica-set tutorial/convert-secondary-into-arbiter diff --git a/source/tutorial/convert-standalone-to-replica-set.txt b/source/tutorial/convert-standalone-to-replica-set.txt index 81c63a29ec7..cb186d781a4 100644 --- a/source/tutorial/convert-standalone-to-replica-set.txt +++ b/source/tutorial/convert-standalone-to-replica-set.txt @@ -23,7 +23,7 @@ administration `, see: Procedure --------- -These procedures assume you have a :term:`standalone` instance of MongoDB +This procedure assumes you have a :term:`standalone` instance of MongoDB installed. If you have not already installed MongoDB, see the :ref:`installation tutorials `. diff --git a/source/tutorial/force-member-to-be-primary.txt b/source/tutorial/force-member-to-be-primary.txt new file mode 100644 index 00000000000..0be8bfe23f6 --- /dev/null +++ b/source/tutorial/force-member-to-be-primary.txt @@ -0,0 +1,24 @@ +========================== +For a Member to be Primary +========================== + +.. default-domain:: mongodb + +Synopsis +-------- + +You can force a member to be :term:`primary` by giving it a higher +:data:`members[n].priority` value than any other member in the +:term:`replica set`. You can also force :term:`secondary` members never +to become primary by setting their :data:`members[n].priority` values to +``0``, which means they can never seek :ref:`election +` as primary. For more information on priority +levels, see :ref:`replica-set-node-priority`. + +Procedures +---------- + +.. _replica-set-force-member-to-be-primary-via-priority-setting: + +Force a Member to be Primary by Setting it Priority High +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~