-
-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: user sessions are never properly cleaned up when a node dies #25
Comments
No, this is just short hand property syntax and is exactly the same functionally. Can you give further details about the issue? |
Hey @copleykj – thanks for the prompt reply! I did some additional troubleshooting and it seems that the varying issues I'm experiencing are likely related to the fact I'm using https://github.com/cult-of-coders/redis-oplog instead of Meteor's built-in. I'll likely have to wind up rolling something of my own unfortunately. I'll go ahead and close this issue. Cheers! |
I'm gonna reopen this cause the rest of the packages in this set are built to work with redis-oplog and if something about it breaks this package I want to understand what might cause this and fix it. |
Sure thing. The key issue seems to be that that redis oplog doesn't have any means of detecting the db TTL/record expiry that the server presence package relies on: The workaround I've implemented is to use the https://www.npmjs.com/package/mongo-oplog2/v/2.1.2 package and tail the oplog myself -> push the changes to redis so that the logic in the server presence package associated with Workaround:
Hope that helps! |
Perhaps I'm overlooking something, but it seems that this query should be
{ serverId: serverId }
instead, yes?Thanks!
socialize-user-presence/server/user-presence.js
Line 148 in 8e8d6fe
The text was updated successfully, but these errors were encountered: