Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-27918

Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.1
    • Component/s: Replication
    • None
    • ALL
    • Hide

      1. You need to habe ca. 10 Gb Database in Replica Set with 1 master and no secondaries.
      2. Add new secondary member.
      3. Init sync from master
      3. After init sync you should have a replication lag. Sometimes this lag occurs after 2-3 days.

      Show
      1. You need to habe ca. 10 Gb Database in Replica Set with 1 master and no secondaries. 2. Add new secondary member. 3. Init sync from master 3. After init sync you should have a replication lag. Sometimes this lag occurs after 2-3 days.

      Please help me with this very big replication lag.

      Unable to find source-code formatter for language: log. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      db.printReplicationInfo()
      configured oplog size:   9458.8388671875MB
      log length start to end: 1433730secs (398.26hrs)
      oplog first event time:  Thu Jan 19 2017 19:25:06 GMT+0000 (UTC)
      oplog last event time:   Sun Feb 05 2017 09:40:36 GMT+0000 (UTC)
      now:                     Sun Feb 05 2017 09:40:36 GMT+0000 (UTC)
      

      Log from secondary member: There are very man these entires:

      Unable to find source-code formatter for language: log. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
      2017-02-05T10:36:09.129+0000 I ASIO     [NetworkInterfaceASIO-RS-0] Connecting to xxx:27017
      2017-02-05T10:36:09.131+0000 I ASIO     [NetworkInterfaceASIO-RS-0] Successfully connected to xxx:27017
      2017-02-05T10:36:19.725+0000 I REPL     [replication-334] Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand 2783292 -- target:xxx:27017 db:local expDate:2017-02-05T10:36:19.725+0000 cmd:{ getMore: 13866089092, collection: "oplog.rs", maxTimeMS: 5000, term: 262, lastKnownCommittedOpTime: { ts: Timestamp 1486220253000|22, t: 262 } }. Last fetched optime (with hash): { ts: Timestamp 1486220260000|13, t: 262 }[846203197011982456]. Restarts remaining: 3
      2017-02-05T10:36:19.725+0000 I REPL     [replication-334] Scheduled new oplog query Fetcher source: xxx:27017 database: local query: { find: "oplog.rs", filter: { ts: { $gte: Timestamp 1486220260000|13 } }, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000, term: 262 } query metadata: { $replData: 1, $ssm: { $secondaryOk: true } } active: 1 timeout: 10000ms inShutdown: 0 first: 1 firstCommandScheduler: RemoteCommandRetryScheduler request: RemoteCommand 2783320 -- target:xxx:27017 db:local cmd:{ find: "oplog.rs", filter: { ts: { $gte: Timestamp 1486220260000|13 } }, tailable: true, oplogReplay: true, awaitData: true, maxTimeMS: 60000, term: 262 } active: 1 callbackHandle.valid: 1 callbackHandle.cancelled: 0 attempt: 1 retryPolicy: RetryPolicyImpl maxAttempts: 1 maxTimeMillis: -1ms
      ...
      

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            vingrad Vladimir
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: