Closed dottodot closed 4 years ago
This releated to https://github.com/feathersjs-ecosystem/feathers-sync/issues/94, beacuse of the leak the app keeps crashing which causes this error.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Apologies if the issue could not be resolved. FeathersJS ecosystem modules are community maintained so there may be a chance that there isn't anybody available to address the issue at the moment. For other ways to get help see here.
I am experience this issue as well. How comes this is related to the memory leak, if any?
And: How to circumvent this issue? Any workarounds found?
Just tested it with Redis. It works as aspected.
Would be nice to know why Mubsub breaks here. Because with Redis, I have another dependency which makes the app more complex.
Looking at other issues like #110 and #119 it looks like Mubsub just doesn't work very well with newer versions and does not appear to be maintained anymore. I'm inclined to remove it.
@daffl I want to try to fix this, as it is preventing me from using multiple concurrence. Any tips before I start?
I was planning on completely replacing mubsub with a from-scratch implementation of a MongoDB collection watcher but didn't get to it yet.
I have 2 apps both using
feathers-sync
, both on the same servers and both connecting the same mongo replica set although using seperate databases. But on one of the app I keep getting this error.I'm posting in here as
feathers-sync
is the only package I have installed that usesmubsub
which hasn't been updated in a while and doesn't look like any of the issues are being answered.