Skip to content

Commit 092838c

Browse files
author
Bob Grabar
committed
DOCS-246 added an include on changing oplog size
1 parent 18619af commit 092838c

File tree

3 files changed

+43
-3
lines changed

3 files changed

+43
-3
lines changed

source/administration/replica-sets.txt

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,10 +21,13 @@ suggestions for administers of replica sets.
2121
The following tutorials provide task-oriented instructions for
2222
specific administrative tasks related to replica set operation.
2323

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`
2626
- :doc:`/tutorial/convert-replica-set-to-replicated-shard-cluster`
27+
- :doc:`/tutorial/convert-secondary-into-arbiter`
2728
- :doc:`/tutorial/deploy-geographically-distributed-replica-set`
29+
- :doc:`/tutorial/deploy-replica-set`
30+
- :doc:`/tutorial/expand-replica-set`
2831

2932
.. _replica-set-node-configurations:
3033
.. _replica-set-member-configurations:
@@ -484,6 +487,15 @@ of the member with the highest :data:`members[n].priority` setting.
484487
<replica-set-reconfiguration-usage>` example revolves around
485488
changing the priorities of the :data:`members` of a replica set.
486489

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+
487499
.. _replica-set-security:
488500

489501
Security
Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
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.

source/tutorial/change-oplog-size.txt

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,14 @@ oplog size affects :term:`delayed members <delayed member>` and affects
2020
topic and the :ref:`replica-set-replication-lag` topic in
2121
:doc:`/administration/replica-sets`.
2222

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+
2331
Procedure
2432
---------
2533

@@ -32,7 +40,7 @@ The examples in this procedure use the following configuration:
3240
- The replica set is running with a :setting:`data directory <dbpath>`
3341
of ``/srv/mongodb``.
3442

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
3644
then restart it in "standalone" mode running on a different port.
3745
Note that shutting down the primary will trigger a failover situation
3846
and another member in the replica set will become primary.

0 commit comments

Comments
 (0)