[SERVER-39110] Fetcher stopped querying remote oplog with error: InvalidSyncSource: Sync source's last applied OpTime { ts: Timestamp 150|605, t: 60 } is not greater than our last fetched OpTime { ts: Timestamp 15470|605, t: 60 }. Choosing new sync source. Created: 21/Jan/19  Updated: 23/Jan/19  Resolved: 23/Jan/19

Status: Closed
Project: Core Server
Component/s: Admin, Replication
Affects Version/s: 3.4.18
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: ashok Assignee: Eric Sedor
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Mongodb sharded cluster


Participants:

 Description   

we are having one primary, secondary and arbiter in replica set so we are recieving errors in our secondary instances so what causes the errors and is there any risk factor to our cluster what are requirements to stop these errors please find the attachment of errors and please give solution.

 

Log File Monitoring : key = error, File = /var/log/mongodb/mongod.log (host11:log[/var/log/mongodb/mongod.log,@mongodb_error,UTF-8]): 2019-01-20T02:03:02.174+0900 W REPL [rsBackgroundSync] Fetcher stopped querying remote oplog with error: InvalidSyncSource: Sync source's last applied OpTime { ts: Timestamp 1547917372000|605, t: 60 } is not greater than our last fetched OpTime { ts: Timestamp 1547917372000|605, t: 60 }. Choosing new sync source.
Log File Monitoring : key = error, File = /var/log/mongodb/mongod.log (host14:log[/var/log/mongodb/mongod.log,@mongodb_error,UTF-8]): 2019-01-18T01:57:58.646+0900 W REPL [rsBackgroundSync] Fetcher stopped querying remote oplog with error: InvalidSyncSource: Sync source's last applied OpTime { ts: Timestamp 1547744268000|2966, t: 58 } is not greater than our last fetched OpTime { ts: Timestamp 1547744268000|2966, t: 58 }. Choosing new sync source.
Log File Monitoring : key = error, File = /var/log/mongodb/mongod.log (host11:log[/var/log/mongodb/mongod.log,@mongodb_error,UTF-8]): 2019-01-15T03:52:13.002+0900 W REPL [rsBackgroundSync] Fetcher stopped querying remote oplog with error: InvalidSyncSource: Sync source's last applied OpTime { ts: Timestamp 1547491922000|3629, t: 60 } is not greater than our last fetched OpTime { ts: Timestamp 1547491922000|3629, t: 60 }. Choosing new sync sourc



 Comments   
Comment by Eric Sedor [ 23/Jan/19 ]

Hello, this log line is not alarming by itself but it could be part of a larger issue. We recommend investigating the health of the deployment and in particular recommend care when using arbiter-based configurations.

However, the SERVER project is for reporting bugs or feature suggestions and we don't see a reason to believe there is a bug around this at this time. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-user group.

Generated at Thu Feb 08 04:51:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.