Allow configuration of timeouts for getMores on oplog for 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:`

}. 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?