1
1
ref : transactions-read-pref
2
2
content : |
3
3
4
- :doc :`Multi-document transactions </core/ transactions>` that contain
4
+ :ref :`Multi-document transactions <transactions>` that contain
5
5
read operations must use read preference :readmode:`primary`. All
6
6
operations in a given transaction must route to the same member.
7
7
@@ -22,7 +22,7 @@ content: |
22
22
23
23
For additional transactions usage considerations
24
24
(such as runtime limit and oplog size limit), see also
25
- :doc:`/core/transactions- production-consideration `.
25
+ :ref:`< production-considerations> `.
26
26
27
27
---
28
28
ref : transactions-intro
@@ -47,7 +47,7 @@ content: |
47
47
multi-document transactions on replica sets.
48
48
49
49
For details regarding transactions in MongoDB, see the
50
- :doc:`/core/ transactions` page.
50
+ :ref:` transactions <transactions> ` page.
51
51
52
52
---
53
53
ref : transactions-faq
@@ -75,7 +75,7 @@ content: |
75
75
multi-document transactions on replica sets.
76
76
77
77
For details regarding transactions in MongoDB, see the
78
- :doc:`/core/ transactions` page.
78
+ :ref:` transactions <transactions> ` page.
79
79
80
80
---
81
81
ref : transactions-operations-restrictions
@@ -139,11 +139,11 @@ content: |
139
139
140
140
.. include:: /includes/extracts/transactions-cross-shard-collection-restriction.rst
141
141
142
- - You cannot write to :doc :`capped </core/ capped-collections >`
142
+ - You cannot write to :ref :`capped <manual- capped-collection >`
143
143
collections. (Starting in MongoDB 4.2)
144
144
145
145
- You cannot use read concern :readconcern:`"snapshot"` when reading
146
- from a :doc :`capped </core/ capped-collections >` collection.
146
+ from a :ref :`capped <manual- capped-collection >` collection.
147
147
(Starting in MongoDB 5.0)
148
148
149
149
- You cannot read/write to collections in the ``config``, ``admin``,
@@ -191,8 +191,8 @@ content: |
191
191
ref : transactions-supported-operation
192
192
content : |
193
193
194
- |operation| can be used inside :doc :`multi-document transactions
195
- </core/ transactions>`.
194
+ |operation| can be used inside :ref :`multi-document transactions
195
+ <transactions>`.
196
196
197
197
---
198
198
ref : transactions-distinct-support
@@ -275,7 +275,7 @@ content: |
275
275
ref : transactions-read-concern-majority
276
276
content : |
277
277
Disabling :readconcern:`"majority"` read concern affects support for
278
- :doc :`transactions </core/ transactions>` on sharded clusters. Specifically:
278
+ :ref :`transactions <transactions>` on sharded clusters. Specifically:
279
279
280
280
- A transaction cannot use read concern :readconcern:`"snapshot"` if
281
281
the transaction involves a shard that has :ref:`disabled read
@@ -285,7 +285,7 @@ content: |
285
285
transaction's read or write operations involves a shard that has
286
286
disabled read concern :readconcern:`"majority"`.
287
287
288
- However, it does not affect :doc :`transactions </core/ transactions>`
288
+ However, it does not affect :ref :`transactions <transactions>`
289
289
on replica sets. For transactions on replica sets, you can specify
290
290
read concern :readconcern:`"majority"` (or :readconcern:`"snapshot"`
291
291
or :readconcern:`"local"` ) for multi-document transactions even if
@@ -402,31 +402,31 @@ content: |
402
402
403
403
You cannot run transactions on a sharded cluster that has a shard
404
404
with :rsconf:`writeConcernMajorityJournalDefault` set to ``false``
405
- (such as a shard with a voting member that uses the :doc :`in-memory
406
- storage engine </core/ inmemory>`).
405
+ (such as a shard with a voting member that uses the :ref :`in-memory
406
+ storage engine <storage- inmemory>`).
407
407
408
408
---
409
409
ref : transactions-killop-change
410
410
content : |
411
411
412
412
Starting in MongoDB 4.2, you cannot specify :dbcommand:`killCursors` as
413
- the first operation in a :doc :`transaction </core/ transactions>`.
413
+ the first operation in a :ref :`transaction <transactions>`.
414
414
415
415
---
416
416
ref : transactions-capped-collection-change
417
417
content : |
418
418
419
- Starting in MongoDB 4.2, you cannot write to :doc :`capped
420
- </core/ capped-collections >` collections in :doc :`transactions
421
- </core/ transactions>`.
419
+ Starting in MongoDB 4.2, you cannot write to :ref :`capped
420
+ <manual- capped-collection >` collections in :ref :`transactions
421
+ <transactions>`.
422
422
423
423
---
424
424
ref : transactions-capped-collection-read-change
425
425
content : |
426
426
427
427
Starting in MongoDB 5.0, you cannot use read concern
428
428
:readconcern:`"snapshot"` when reading from a
429
- :doc :`capped </core/ capped-collections >` collection.
429
+ :ref :`capped <manual- capped-collection >` collection.
430
430
431
431
---
432
432
ref : transactions-arbiters
@@ -473,14 +473,14 @@ content: |
473
473
ref : transactions-inmemory-txn-page
474
474
content : |
475
475
476
- Starting in MongoDB 4.2, :doc :`multi-document transactions
477
- </core/ transactions>` are supported on replica sets and sharded
476
+ Starting in MongoDB 4.2, :ref :`multi-document transactions
477
+ <transactions>` are supported on replica sets and sharded
478
478
clusters where:
479
479
480
480
- the primary uses the WiredTiger storage engine, and
481
481
482
- - the secondary members use either the WiredTiger storage engine or the
483
- :doc :`in-memory </core/ inmemory>` storage engines.
482
+ - the secondary members use either the WiredTiger storage engine or
483
+ the :ref :`in-memory <storage- inmemory>` storage engines.
484
484
485
485
In MongoDB 4.0, only replica sets using the WiredTiger storage
486
486
engine supported transactions.
@@ -490,7 +490,7 @@ content: |
490
490
You cannot run transactions on a sharded cluster that has a shard
491
491
with :rsconf:`writeConcernMajorityJournalDefault` set to
492
492
``false``, such as a shard with a voting member that uses the
493
- :doc:` in-memory storage engine </core/inmemory>` .
493
+ in-memory storage engine.
494
494
495
495
---
496
496
ref : transactions-inmemory-storage-page
@@ -499,11 +499,11 @@ content: |
499
499
Starting in MongoDB 4.2, transactions are supported on replica sets
500
500
and sharded clusters where:
501
501
502
- - the primary uses the :doc :`WiredTiger </core/ wiredtiger>` storage
502
+ - the primary uses the :ref :`WiredTiger <storage- wiredtiger>` storage
503
503
engine, and
504
504
505
505
- the secondary members use either the WiredTiger storage engine or the
506
- :doc :`in-memory </core/ inmemory>` storage engines.
506
+ :ref :`in-memory <storage- inmemory>` storage engines.
507
507
508
508
In MongoDB 4.0, only replica sets using the WiredTiger storage
509
509
engine supported transactions.
@@ -513,7 +513,7 @@ content: |
513
513
You cannot run transactions on a sharded cluster that has a shard
514
514
with :rsconf:`writeConcernMajorityJournalDefault` set to
515
515
``false``, such as a shard with a voting member that uses the
516
- :doc :`in-memory storage engine </core/ inmemory>`.
516
+ :ref :`in-memory storage engine <storage- inmemory>`.
517
517
---
518
518
ref : transactions-sharded-clusters-commit-writeconcern
519
519
content : |
0 commit comments