Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Done
-
3.3.10
-
None
-
Fully Compatible
-
ALL
-
-
Repl 2016-09-19, Repl 2016-10-10
-
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
|
Attachments
Issue Links
- is related to
-
SERVER-24088 oplog fetcher should retry on getMore ExceededTimeLimit
-
- Closed
-
-
SERVER-26220 Using stopOplogFetcher failpoint causes CPU looping
-
- Closed
-
-
SERVER-35200 Speed up failure detection in the OplogFetcher during steady state replication
-
- Closed
-
- related to
-
SERVER-25966 Add initial sync unittests for metadata retries
-
- Closed
-
-
SERVER-26494 remove unreachable else-branch in sync_source_feedback.cpp logic
-
- Closed
-