Skip to content

Commit e57fd5d

Browse files
author
Sam Kleinman
committed
DOCS-3350: minor edits
1 parent d57f2ed commit e57fd5d

7 files changed

+64
-64
lines changed

source/includes/fact-2.0-fsync-lock-change.rst

Lines changed: 0 additions & 10 deletions
This file was deleted.
Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
title: Flush writes to disk and lock the database to prevent further writes.
22
stepnum: 1
33
ref: flush
4+
pre: |
5+
To flush writes to disk and to "lock" the database, issue the
6+
:method:`db.fsyncLock()` method in the :program:`mongo` shell:
47
action:
5-
pre: |
6-
To flush writes to disk and to "lock" the database, issue the
7-
:method:`db.fsyncLock()` method in the :program:`mongo` shell:
88
language: javascript
99
code: |
1010
db.fsyncLock();
@@ -16,15 +16,13 @@ ref: backup
1616
title: "After the snapshot completes, unlock the database."
1717
stepnum: 3
1818
ref: unlock
19+
pre: |
20+
To unlock the database after the snapshot has completed, use the
21+
following command in the :program:`mongo` shell:
1922
action:
20-
- pre: |
21-
To unlock the database after the snapshot has completed, use the
22-
following command in the :program:`mongo` shell:
23-
language: javascript
24-
code: |
25-
db.fsyncUnlock();
23+
language: javascript
24+
code: |
25+
db.fsyncUnlock();
2626
post: |
2727
.. include:: /includes/warning-fsync-lock-mongodump.rst
28-
29-
.. include:: /includes/fact-2.0-fsync-lock-change.rst
3028
...

source/includes/steps-recover-data-with-repairpath.yaml

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,12 @@
11
title: "Start :program:`mongod` using the option to replace the original files with the repaired files."
22
stepnum: 1
33
ref: start-with-repair
4+
pre: |
5+
Start the :program:`mongod` instance using the :option:`--repair
6+
<mongod --repair>` option **and** the :option:`--repairpath
7+
<mongod --repairpath>` option. Issue a command similar to the
8+
following:
49
action:
5-
pre: |
6-
Start the :program:`mongod` instance using the :option:`--repair
7-
<mongod --repair>` option **and** the :option:`--repairpath <mongod
8-
--repairpath>` option. Issue a command similar to the following:
910
language: sh
1011
code: |
1112
mongod --dbpath /data/db --repair --repairpath /data/db0
@@ -16,10 +17,10 @@ post: |
1617
title: "Start :program:`mongod` with the new data directory."
1718
stepnum: 2
1819
ref: start-with-new-path
20+
pre: |
21+
Start :program:`mongod` using the following invocation to point the
22+
:setting:`~storage.dbPath` at ``/data/db0``:
1923
action:
20-
pre: |
21-
Start :program:`mongod` using the following invocation to point the
22-
:setting:`~storage.dbPath` at ``/data/db0``:
2324
language: sh
2425
code: |
2526
mongod --dbpath /data/db0

source/includes/steps-recover-data-without-repairpath.yaml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ post: |
1414
title: "Start :program:`mongod` using the option to replace the original files with the repaired files."
1515
stepnum: 2
1616
ref: start-with-repair
17+
pre: |
18+
Start the :program:`mongod` instance using the :option:`--repair
19+
<mongod --repair>` option, which replaces the original data files with
20+
the repaired data files. Issue a command similar to the following:
1721
action:
18-
pre: |
19-
Start the :program:`mongod` instance using the :option:`--repair
20-
<mongod --repair>` option, which replaces the original data files with
21-
the repaired data files. Issue a command similar to the following:
2222
language: sh
2323
code: |
2424
mongod --dbpath /data/db --repair
@@ -29,10 +29,10 @@ post: |
2929
title: "Start :program:`mongod` as usual."
3030
stepnum: 3
3131
ref: start-as-usual
32+
pre: |
33+
Start :program:`mongod` using the following invocation to point the
34+
:setting:`~storage.dbPath` at ``/data/db``:
3235
action:
33-
pre: |
34-
Start :program:`mongod` using the following invocation to point the
35-
:setting:`~storage.dbPath` at ``/data/db``:
3636
language: sh
3737
code: |
3838
mongod --dbpath /data/db

source/includes/steps-restore-primary-from-backup.yaml

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -16,23 +16,23 @@ content: |
1616
title: "Start a :program:`mongod` using data files from the backup as the data path."
1717
stepnum: 2
1818
ref: start
19+
pre: |
20+
The following example uses ``/data/db`` as the data path, as specified
21+
in the :setting:`dbpath` setting:
1922
action:
20-
pre: |
21-
The following example uses ``/data/db`` as the data path, as specified
22-
in the :setting:`dbpath` setting:
2323
language: sh
2424
code: |
2525
mongod --dbpath /data/db
2626
---
2727
title: "Convert the standalone :program:`mongod` to a single-node replica set"
2828
stepnum: 3
2929
ref: convert
30+
pre: |
31+
Convert the standalone :program:`mongod` process to a single-node
32+
replica set by shutting down the :program:`mongod` instance, and
33+
restarting it with the :option:`--replSet <mongod --replSet>` option,
34+
as in the following example:
3035
action:
31-
pre: |
32-
Convert the standalone :program:`mongod` process to a single-node
33-
replica set by shutting down the :program:`mongod` instance, and
34-
restarting it with the :option:`--replSet <mongod --replSet>` option,
35-
as in the following example:
3636
language: sh
3737
code: |
3838
mongod --dbpath /data/db --replSet <replName>
@@ -44,19 +44,21 @@ post: |
4444
title: Connect to the :program:`mongod` instance.
4545
stepnum: 4
4646
ref: connect
47+
pre: |
48+
For example, first use the following command to a :program:`mongod`
49+
instance running on the localhost interface:
4750
action:
48-
pre: |
49-
For example, first issue the following to connect:
5051
language: sh
5152
code: |
5253
mongo
5354
---
5455
title: Initiate the new replica set.
5556
stepnum: 5
5657
ref: initiate
58+
pre: |
59+
Use :method:`rs.initiate()` to initiate the new replica set, as in
60+
the following example:
5761
action:
58-
pre: |
59-
Issue :method:`rs.initiate()` to initiate the new replica set. For example:
6062
language: javascript
6163
code: |
6264
rs.initiate()

source/includes/steps-restore-sharded-cluster-with-snapshots.yaml

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ pre: |
66
all shards *and* all config servers.
77
action:
88
pre: |
9-
Connect to each member and issue the following:
9+
Connect to each member use the following operation:
1010
language: javascript
1111
code: |
1212
use admin
@@ -33,11 +33,11 @@ action:
3333
title: Restart the config servers.
3434
stepnum: 3
3535
ref: restart-config-servers
36+
pre: |
37+
Restart each :ref:`config server <sharding-config-server>`
38+
:program:`mongod` instance by issuing a command similar to the
39+
following for each, using values appropriate to your configuration:
3640
action:
37-
pre: |
38-
Restart each :ref:`config server <sharding-config-server>`
39-
:program:`mongod` instance by issuing a command similar to the
40-
following for each, using values appropriate to your configuration:
4141
language: sh
4242
code: |
4343
mongod --configsvr --dbpath /data/configdb --port 27019
@@ -67,11 +67,11 @@ content: |
6767
title: "Connect to a :program:`mongos` to ensure the cluster is operational."
6868
stepnum: 7
6969
ref: ensure
70+
pre: |
71+
Connect to a :program:`mongos` instance from a :program:`mongo` shell
72+
and use the :method:`db.printShardingStatus()` method to ensure that
73+
the cluster is operational, as follows:
7074
action:
71-
pre: |
72-
Connect to a :program:`mongos` instance from a :program:`mongo` shell
73-
and use the :method:`db.printShardingStatus()` method to ensure that
74-
the cluster is operational, as follows:
7575
language: javascript
7676
code: |
7777
db.printShardingStatus()

source/tutorial/backup-sharded-cluster-with-filesystem-snapshots.txt

Lines changed: 17 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,21 @@ particular.
2222

2323
.. include:: /includes/note-shard-cluster-backup.rst
2424

25-
Procedure
26-
---------
25+
Considerations
26+
--------------
27+
28+
Balancing
29+
~~~~~~~~~
30+
31+
It is *essential* that you stop the balancer before capturing a
32+
backup.
33+
34+
If the balancer is active while you capture backups, the backup
35+
artifacts may be incomplete and/or have duplicate data, as :term:`chunks
36+
<chunk>` may migrate while recording backups.
37+
38+
Precision
39+
~~~~~~~~~
2740

2841
In this procedure, you will stop the cluster balancer and take a backup
2942
up of the :term:`config database`, and then take backups of each
@@ -37,11 +50,7 @@ of the backup while minimizing impact on the cluster by taking the
3750
backup from a secondary member of the replica set that provides each
3851
shard.
3952

40-
.. warning::
41-
42-
It is essential that you stop the balancer before creating
43-
backups. If the balancer remains active, your resulting backups
44-
could have duplicate data or miss some data, as :term:`chunks
45-
<chunk>` may migrate while recording backups.
53+
Procedure
54+
---------
4655

4756
.. include:: /includes/steps/backup-sharded-cluster-with-snapshots.rst

0 commit comments

Comments
 (0)