Repository navigation
io.fetchSockets() sometimes works across instances, sometimes not #557
Description
I have an app where I need to send a list of all connected clients and rooms to all connected clients.
Sometimes I'm able to get all clients across multiple instances with io.fetchSockets() and other times it will only grab clients from the same instance.
I'm not exactly sure what to try at this point, but I'm almost certain this has to be the issue.
Here is related dependencies:
"@socket.io/redis-adapter": "^8.3.0",
"socket.io": "^4.8.1",
"socket.io-client": "^4.8.1"
"ioredis": "^5.5.0",
Activity
vybhavpai-gush commentedon May 20, 2026
facing something similar, any solutions or planned fixes?
dizzyjaguar commentedon May 20, 2026
@vybhavpai-gush No, I changed my architecture so I'm just running one Websocket Server now. So I haven't been dealing with issue. (till I need to scale up)
vybhavpai-gush commentedon May 21, 2026
really appreciate you getting back, thank you :) We are considering maintaining socket liveness via heart beat events being stored in redis per socket. not the cleanest solution, will post here if we find something else!
vybhavpai-gush commentedon May 22, 2026
Hey @dizzyjaguar id like to know more about your implementation. We are running multiple EC2 instances which act as our chat servers and use redis adapter for establishing cross instance communication. message relaying works like a charm across but only fetch sockets doesnt work.
interestingly(as every developer says) this works on my local
I was suspecting this might have to do with AWS' setup and wanted to know what you have built