We’ve been noticing this a lot of late (maybe up to 10 times in a day and then nothing some others) and can’t figure out the root cause. It seems related to us updating to 2.7.3 (from 2.5.8 - we’re slowing catching up ) and also upgraded the DB to 5.0. There’s really nothing on the internet regarding this so wondering if maybe some of you have ever seen it before?
Here’s the full callstack
message: Error in oplog callback: insert found for already-existing ID in published
stack:
Error: insert found for already-existing ID in published
at packages/mongo/oplog_observe_driver.js:596:17
at Object.Meteor._noYieldsAllowed (packages/meteor.js:783:12)
at OplogObserveDriver._handleOplogEntrySteadyOrFetching (packages/mongo/oplog_observe_driver.js:579:12)
at OplogObserveDriver.proto._handleOplogEntrySteadyOrFetching (packages/montiapm:agent/lib/hijack/wrap_observers.js:35:53)
at packages/mongo/oplog_observe_driver.js:133:20
at packages/mongo/oplog_observe_driver.js:17:9
at Object.Meteor._noYieldsAllowed (packages/meteor.js:783:12)
at packages/mongo/oplog_observe_driver.js:121:16
at packages/mongo/oplog_tailing.js:108:7
at runWithEnvironment (packages/meteor.js:1320:24)
at Object.callback (packages/meteor.js:1333:14)
at packages/ddp-server/crossbar.js:114:36
at Array.forEach (<anonymous>)
at Function._.each._.forEach (packages/underscore.js:139:11)
at DDPServer._Crossbar.fire (packages/ddp-server/crossbar.js:112:7)
at DDPServer._Crossbar.kadira_Crossbar_fire [as fire] (packages/montiapm:agent/lib/hijack/set_labels.js:102:33)
We’re going to look at adding meteorx so we can add a more informative error when this happens and try pinpoint it.