File tree Expand file tree Collapse file tree 3 files changed +43
-3
lines changed Expand file tree Collapse file tree 3 files changed +43
-3
lines changed Original file line number Diff line number Diff line change @@ -21,10 +21,13 @@ suggestions for administers of replica sets.
21
21
The following tutorials provide task-oriented instructions for
22
22
specific administrative tasks related to replica set operation.
23
23
24
- - :doc:`/tutorial/deploy -replica-set`
25
- - :doc:`/tutorial/expand-replica-set `
24
+ - :doc:`/tutorial/change-hostnames-in-a -replica-set`
25
+ - :doc:`/tutorial/change-oplog-size `
26
26
- :doc:`/tutorial/convert-replica-set-to-replicated-shard-cluster`
27
+ - :doc:`/tutorial/convert-secondary-into-arbiter`
27
28
- :doc:`/tutorial/deploy-geographically-distributed-replica-set`
29
+ - :doc:`/tutorial/deploy-replica-set`
30
+ - :doc:`/tutorial/expand-replica-set`
28
31
29
32
.. _replica-set-node-configurations:
30
33
.. _replica-set-member-configurations:
@@ -484,6 +487,15 @@ of the member with the highest :data:`members[n].priority` setting.
484
487
<replica-set-reconfiguration-usage>` example revolves around
485
488
changing the priorities of the :data:`members` of a replica set.
486
489
490
+ Changing Oplog Size
491
+ ~~~~~~~~~~~~~~~~~~~
492
+
493
+ The following is an overview of the procedure for changing the size of the oplog:
494
+
495
+ .. include:: /includes/procedure-change-oplog-size.rst
496
+
497
+ For a detailed procedure, see :doc:`/tutorial/change-oplog-size`.
498
+
487
499
.. _replica-set-security:
488
500
489
501
Security
Original file line number Diff line number Diff line change
1
+ 1. Shut down the current :term: `primary ` instance in the
2
+ :term: `replica set ` and then restart it on a different port
3
+ and in "standalone" mode.
4
+
5
+ #. Create a backup of the old (current) oplog. This is optional.
6
+
7
+ #. Save the last entry from the old oplog.
8
+
9
+ #. Drop the old oplog.
10
+
11
+ #. Create a new oplog of a different size.
12
+
13
+ #. Insert the previously saved last entry from the old oplog into the
14
+ new oplog.
15
+
16
+ #. Restart the server as a member of the replica set on its usual
17
+ port.
18
+
19
+ #. Apply this procedure to any other member of the replica set that
20
+ *could become * primary.
Original file line number Diff line number Diff line change @@ -20,6 +20,14 @@ oplog size affects :term:`delayed members <delayed member>` and affects
20
20
topic and the :ref:`replica-set-replication-lag` topic in
21
21
:doc:`/administration/replica-sets`.
22
22
23
+ Overview
24
+ --------
25
+
26
+ The following is an overview of the procedure for changing the size of
27
+ the oplog:
28
+
29
+ .. include:: /includes/procedure-change-oplog-size.rst
30
+
23
31
Procedure
24
32
---------
25
33
@@ -32,7 +40,7 @@ The examples in this procedure use the following configuration:
32
40
- The replica set is running with a :setting:`data directory <dbpath>`
33
41
of ``/srv/mongodb``.
34
42
35
- 1. Shutdown the current :term:`primary` instance in the replica set and
43
+ 1. Shut down the current :term:`primary` instance in the replica set and
36
44
then restart it in "standalone" mode running on a different port.
37
45
Note that shutting down the primary will trigger a failover situation
38
46
and another member in the replica set will become primary.
You can’t perform that action at this time.
0 commit comments