I need to offload connections from the node server to redis, so I could update (and restart) the node server on a live system. Then pull the connections back from redis into node. Is this possible with SockJS connections?
Asked
Active
Viewed 611 times
0
-
I don't see how this would be possible with *any* networking connection. – robertklep Nov 06 '13 at 06:44
-
I thought RedisStore for socket.io allowed to do this. I might be wrong. – Rob Fox Nov 06 '13 at 07:29
-
That uses Redis to pub/sub messages between multiple `socket.io` instances/servers, but not the actual network connections. – robertklep Nov 06 '13 at 07:32
-
Ok, if this is not possible you can add it as an answer :) – Rob Fox Nov 06 '13 at 08:05
-
Let's just wait and see if anyone comes up with an answer :) – robertklep Nov 06 '13 at 08:17
2 Answers
1
I have a suggestion (don't know if it still on time):
There is no way you can store networking connection on wherever (it not serializable in any way, since it is based on OS resources). But you can store on Redis (or any other storage mechanism) all relevant user session state, indexed by an user id of any kind.
In order to recover from a server reboot (or crash), the client could reconnect and given that it knows the user id, it can be reattached to the session state.
If you have any kind of fail over mechanism, or if the reboot process is short enough, your users will feel nothing but a little freezing on communication, if any.
I hope this can help.
Regards.
Heleno
helenov
- 341
- 1
- 2
- 15
0
If you restart your node server all your connections will be lost and your clients will be disconnected, there is no way to store the connections to reboot a server.
Emanuel Ralha
- 754
- 4
- 12
-
If the server restart-cycle completes before the next heartbeat arrive, previously connected clients will reconnect to same server. I think its ***possible***. – dklt Dec 06 '13 at 02:11
-
but the session state will be gone for all the connections i think, correct me if im wrong. – Emanuel Ralha Dec 13 '13 at 18:12
-
reconnecting to the same server would be unlikely to happen since nowadays all web applications runs multiple instances. so something else has to be done. – kroe Jun 24 '15 at 18:53