[SERVER-37346] Restarting oplog query due to error: InterruptedDueToReplStateChange: operation was interrupted Created: 27/Sep/18 Updated: 27/Sep/18 Resolved: 27/Sep/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.4.3 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | ashwin | Assignee: | Nick Brewer |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
we have specup up our mongodb instances each shard conisists of 3 instances primary, secondaray & arbiter at that time in primary instance have executed the command rs.stepdown() and after steeping down i have received this error in all instances. what causes this error Log File Monitoring : key = error, File = /var/log/mongodb/mongod.log (host01:log[/var/log/mongodb/mongod.log,@mongodb_error,UTF-8]): 2018-09-20T02:38:14.332+0900 I REPL [replication-1] Restarting oplog query due to error: InterruptedDueToReplStateChange: operation was interrupted. Last fetched optime (with hash): { ts: Timestamp 1537378260000|1, t: 45 }[1353989873524125418]. Restarts remaining: 3 |
| Comments |
| Comment by ashwin [ 27/Sep/18 ] |
|
this is regarding MongoDB server issue after stepdown we got this alert |
| Comment by Nick Brewer [ 27/Sep/18 ] |
|
bvk Thanks for your report. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. I can see you've posted this question on StackExchange - I would additionally suggest 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. -Nick |