lynchem

It seems actually that the issue is when nothing happens for whatever the oplog 'window' is. See #11993 as well. I think we're also downgrading to 2.5.6 until we get...

Good to get further confirmation of this @zzaacchh. Should be fixed in the 2.8 beta thanks to a fix in v4.9 of the driver. [See this](https://github.com/meteor/meteor/issues/11993#issuecomment-1210989103) for more detail.

So we had a similar-ish case so I thought I'd comment here rather than open a new issue. We had staging and production in the same cluster and when I...

Thanks @fredmaiaarantes for looking at this. Following on from @arggh 's hypothesis. > What is happening here, according to my hypothesis, is that the oplog tailing from the dormant app1...

Any update on this @fredmaiaarantes ? This is still blocking up from upgrading past 2.5.8

Yeah, I think they're all related @derwaldgeist although I think the addition of the oplogv2converter in 2.6 made matters worse. Running 2.5 I don't see any mention of the oplog...

That's interesting @bricous. I hadn't even thought about the mongo server version. We're running 4.2 and I see in the [changelog for 4.4](https://www.mongodb.com/docs/manual/release-notes/4.4/) that a variety of things were changed...

> Stupid question: How do you swap out the driver? I thought it's baked into the Meteor framework somehow. Yeah, the node driver version is determined by the Meteor version...

What version of MongoDB is your server running @Floriferous ?

Actually that templateFunc.name was always set to "bind" so instead we decided to update wrapHelper to take a name parameter which is uses instead of "template helper". Then when calling...