Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
Repl 2018-09-24, Repl 2019-01-14, Repl 2019-01-28, Repl 2019-02-11, Repl 2019-02-25
Attachments
Issue Links
- depends on
-
SERVER-35873 Maintain the oldest oplog entry timestamp of any active transaction
-
- Closed
-
-
SERVER-36501 serverStatus support for prepared transactions
-
- Closed
-
- is documented by
-
DOCS-12470 Docs for SERVER-36489: Start initial sync oplog fetching from the 'oldest active transaction timestamp'
-
- Closed
-
- is related to
-
TOOLS-2088 Support for prepared transactions
-
- Closed
-
-
TOOLS-2225 mongorestore 4.2 transaction support
-
- Closed
-
-
TOOLS-2304 mongodump 4.2 transactions support
-
- Closed
-
-
SERVER-39795 Make sure initial sync starts to sync oplog from the oldest active transaction timestamp
-
- Closed
-
- related to
-
SERVER-39608 Initial syncer oplog fetcher should skip first doc on retries
-
- Closed
-
-
SERVER-39989 Use a config.transactions find command for the begin fetching timestamp in initial sync
-
- Closed
-