[SERVER-36489] Start initial sync oplog fetching from the 'oldest active transaction timestamp' Created: 07/Aug/18  Updated: 29/Oct/23  Resolved: 11/Feb/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.1.8

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Samyukta Lanka
Resolution: Fixed Votes: 0
Labels: prepare_initial_sync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-35873 Maintain the oldest oplog entry times... Closed
depends on SERVER-36501 serverStatus support for prepared tra... Closed
Documented
is documented by DOCS-12470 Docs for SERVER-36489: Start initial ... Closed
Related
related to SERVER-39608 Initial syncer oplog fetcher should s... Closed
related to SERVER-39989 Use a config.transactions find comman... Closed
is related to TOOLS-2088 Support for prepared transactions Closed
is related to TOOLS-2225 mongorestore 4.2 transaction support Closed
is related to TOOLS-2304 mongodump 4.2 transactions support Closed
is related to SERVER-39795 Make sure initial sync starts to sync... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-09-24, Repl 2019-01-14, Repl 2019-01-28, Repl 2019-02-11, Repl 2019-02-25
Participants:

 Comments   
Comment by Githook User [ 11/Feb/19 ]

Author:

{'name': 'Samy Lanka', 'email': 'samy.lanka@mongodb.com', 'username': 'lankas'}

Message: SERVER-36489 Start initial sync oplog fetching from the 'oldest active transaction timestamp'
SERVER-36490 Initial sync should not actually prepare transactions on applying prepareTransaction oplog entries
SERVER-36491 During initial sync, make commitTransaction oplog entries apply the transaction from the prepare oplog entry
Branch: master
https://github.com/mongodb/mongo/commit/4f858c52b05ecc49d2ae19bbaf59fc0aad445b7e

Comment by Samyukta Lanka [ 30/Jan/19 ]

This ticket relies on the existence of the transactions field in the response to serverStatus. This field is included by default for all versions of 4.0 since it was added as a part of SERVER-28923, so there shouldn't be any upgrade/downgrade concerns with that.

Comment by Samyukta Lanka [ 25/Jan/19 ]

code review: https://mongodbcr.appspot.com/240310001/

Generated at Thu Feb 08 04:43:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.