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

Allow configuration of timeouts for getMores on oplog for replication

XMLWordPrintableJSON

    • Type: Icon: New Feature New Feature
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.4.16
    • Component/s: Replication
    • Labels:
      None
    • Replication

      We are running into issues with oplog timeout.

       

      2019-01-14T07:05:11.295+0000 I REPL [replication-175] Restarting oplog query due to error: ExceededTimeLimit: Operation timed out, request was RemoteCommand 1472496 – target:<xxx>:27017 db:local expDate:2019-01-14T07:05:11.295+0000 cmd:{ getMore: 16260654145, collection: "oplog.rs", maxTimeMS: 5000, term: 37, lastKnownCommittedOpTime:`

      { ts: Timestamp 1 547154618000|17, t: 37 }

      }. Last fetched optime (with hash): { ts: Timestamp 1547364761000|168, t: 37 }[-6073438480613680634]. Restarts remaining: 3

       

      As per instructions in text https://jira.mongodb.org/browse/SERVER-19605 we have set 

      setParameter:
      oplogInitialFindMaxSeconds: 600

       

      Is there a separate timeout for the oplog getMore command that is not documented?

       

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            dharshanr@scalegrid.net Dharshan Rangegowda
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: