You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using two version of socket io.
For
v2.5.0 => "socket.io-redis": "^5.4.0"
v4.7.1 => @socket.io/redis-adapter": "^8.0.1"
transport is working fine when we are pushing the messages but whenever we are running const sockets = await io.to('bridge-room').fetchSockets(); on v4.7.1
we get the following error
/node_modules/@socket.io/redis-adapter/dist/index.js:712
reject(new Error("timeout reached while waiting for fetchSockets response"));
^
Error: timeout reached while waiting for fetchSockets response
I have been hitting my head for a while now on this.
The text was updated successfully, but these errors were encountered:
Hi! If I understand correctly, you have a cluster of servers, some in v2.5.0 and some in v4.7.1.
I think the problem is that the fetchSockets() operation was added in v4, so the v4 server sends the operation to all the servers but only other v4 servers respond, so the operation times out (even though the server has received all necessary responses).
Not sure how to handle this though. Maybe some kind of feature detection?
We are using two version of socket io.
For
v2.5.0 => "socket.io-redis": "^5.4.0"
v4.7.1 => @socket.io/redis-adapter": "^8.0.1"
transport is working fine when we are pushing the messages but whenever we are running
const sockets = await io.to('bridge-room').fetchSockets();
on v4.7.1we get the following error
I have been hitting my head for a while now on this.
The text was updated successfully, but these errors were encountered: