Ошибка репликации MongoDB NetworkInterfaceExceededTimeLimit и MaxTimeMSExpired - причины и исправление - PullRequest
0 голосов
/ 08 апреля 2019

В настройках репликации первичного, вторичного и арбитражного URI подключения репликации периодически прерывается, и в журналах отображается ошибка ниже.Пожалуйста, помогите поделиться тем, что может быть проблемой и что было бы рекомендовано исправить для того же.

 NetworkInterfaceExceededTimeLimit: error in fetcher batch callback ::
caused by :: timed out. Last fetched optime (with hash): { ts:
Timestamp(1554364591, 71), t: 65596 }[3697357721798898959]. Restarts
remaining: 1 I REPL     [replication-1] Error returned from oplog
query (no more query restarts left): MaxTimeMSExpired: error in
fetcher batch callback :: caused by :: operation exceeded time limit W
REPL     [rsBackgroundSync] Fetcher stopped querying remote oplog with
error: MaxTimeMSExpired: error in fetcher batch callback :: caused by
:: operation exceeded time limit I REPL     [SyncSourceFeedback]
SyncSourceFeedback error sending update to <ServerFQDN>:27017:
InvalidSyncSource: Sync source was cleared. Was <ServerFQDN>:27017`

I did refer to link: https://stackoverflow.com/questions/44798577/mongodb-replication-timeout

but it does not match the case with ours. The disk drives have enough space. Please help suggest what could be wrong here. Thank you!!

Each time restart the mongo service on both the servers but it does not help. Error keeps coming intermittently.
...