[SERVER-25702] add support to OplogFetcher for restarting oplog query Created: 19/Aug/16  Updated: 23/May/18  Resolved: 26/Sep/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.3.10
Fix Version/s: 3.3.15

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: Benety Goh
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-25966 Add initial sync unittests for metada... Closed
related to SERVER-26494 remove unreachable else-branch in syn... Closed
is related to SERVER-24088 oplog fetcher should retry on getMore... Closed
is related to SERVER-26220 Using stopOplogFetcher failpoint caus... Closed
is related to SERVER-35200 Speed up failure detection in the Opl... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

The OplogFetcher should restart up to N (10) times before failing.

Sprint: Repl 2016-09-19, Repl 2016-10-10
Participants:
Linked BF Score: 0

 Description   

2016-08-18T21:32:21.909+0000 E REPL     [replication-1] Error fetching oplog during initial sync: ExceededTimeLimit: operation exceeded time limit
2016-08-18T21:32:21.922+0000 I REPL     [initial sync] Initial sync finished applying oplog entries.
2016-08-18T21:32:22.584+0000 I REPL     [InitialSyncInserters-config.migrations0] done running the synchronous task.
2016-08-18T21:32:23.035+0000 I REPL     [repl writer worker 5] data clone finished, status: CallbackCanceled: Initial Sync Cancelled.
2016-08-18T21:32:23.123+0000 E REPL     [initial sync] Initial sync attempt failed -- attempts left: 9 cause: ExceededTimeLimit: operation exceeded time limit



 Comments   
Comment by Githook User [ 26/Sep/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-25702 added support to OplogFetcher for restarting oplog query
Branch: master
https://github.com/mongodb/mongo/commit/9a4693efbe83f3c07c751dd608dec69829978ee6

Comment by Githook User [ 23/Sep/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-25702 changed oplogFetcherMaxFetcherRestarts default from 10 to 3
Branch: master
https://github.com/mongodb/mongo/commit/f128617d2447f137e89e17f596acebf5c1bc744b

Comment by Githook User [ 22/Sep/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-25702 added server parameter for oplog fetcher max fetcher restarts
Branch: master
https://github.com/mongodb/mongo/commit/d526f86f4c409ea746bae4ef0b31a13f4db34c60

Comment by Githook User [ 22/Sep/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-25702 added OplogFetcher constructor argument for max fetcher restarts
Branch: master
https://github.com/mongodb/mongo/commit/1be7c1336f137d99042100c4c37cf6ae0e322813

Comment by Githook User [ 21/Sep/16 ]

Author:

{u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}

Message: SERVER-25702 refactor OplogFetcher - convert owned Fetcher to a unique_ptr to support future restartability changes
Branch: master
https://github.com/mongodb/mongo/commit/8d83bf3557329eb3d1747659e6ca310cbdb2343c

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