Multiplexers, Survey Duration Range and OplogTailingin mongo / meteor

Question

I am developing an application with Meteor.js. For this, I have a cluster of mongo instances for tail tail. In addition, I use Kadira to track my applications.

Since I turned on the tail, many of my / sub pubs are slower than before. I see that this is slower when the oplog request has its attribute wasMultiplexerReady set to false, which is the case for most of the observed changes that I see on Kadira.

The problem is that there is NOTHING on the Internet. I searched for any resource about this and how it works, but literally there is nothing.

Can someone give me a hint / explanation about what is going on here? Like this attribute "wasMultiplexerReady", how is it used, how to reduce the calculation time of the tail of the oplog, etc.?

Thanks.

Answer 1

I know that this is quite late, and I'm not 100% at it, but I think that the subscription has already been signed. The value of another client is already subscribed to this cursor, and the Meteor can simply send the same results to several people.