Overwriting OplogHandle
See original GitHub issue@theodorDiaconu Have you ever considered overwriting OplogHandle class from Meteor’s mongo
package?
I had a quick look and it seems like all the logic specific to mongo oplog tailing is already abstracted to this class.
It might be an interesting alternative to make the package smaller and more tightly bound with observer mechanisms in Meteor core.
I’d be interested to hear your thoughts on this matter.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Everything You Want to Know about Overwrite - MiniTool
The word overwrite meaning is that it writes over the deleted data with new data, that's why the name is. The process of...
Read more >What is Overwrite? - Computer Hope
In general, overwrite is a term used to describe when new information replaces old information or data. For example, in a text editor, ......
Read more >ORA-33000 to ORA-37999 - Oracle Help Center
ORA-36887: (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column. Cause: The column name passes does not...
Read more >Meteor server doesn't recover from mongo server connection
app/web.1 at OplogHandle. ... I see there is an option to override connection parameters, but retry count and reconnect interval both get ...
Read more >reactioncommerce/installation - Gitter
@Allegany cd into your reaction directory and run ln -s docker-compose.dev.yml docker-compose.override.yml . Do you get an error when doing so? Allegany.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, we’re still using the package in production. As I speak, we’re running on 10 quad containers for 6000 connections. Before the integration of the package, this number would have been around 30. Subscription response time is steady under 250 ms, 200ms for method.
An interesting fact is that critical metric switched from CPU to memory with the integration of the package. So we were able to save a couple containers just by bumping up the
max-old-space-size
setting at 3500, CPU still chilling at 50% usage.@simonbelanger yep that is expected since we have a mirror image for every pubsub in the observableCollection, maybe in the future we’re gonna resolve that as well. Very glad it’s a success story for you.