N8n queue mode with clustermode redis

I was trying to configure the n8n deployment to run on clustermode redis (elasticache)

configured following environment variables

QUEUE_BULL_REDIS_CLUSTER_NODES: “node1:6379,node2:6379”
QUEUE_BULL_REDIS_PASSWORD: “”
QUEUE_BULL_REDIS_USERNAME: “default”
QUEUE_BULL_REDIS_DB : “0”
QUEUE_BULL_PREFIX: “n8n-staging”
QUEUE_BULL_REDIS_TLS: “true”

when i run the instance it fails with following error

2025-08-05T09:32:39.704Z | debug | Started Redis cluster client subscriber(n8n) {"scopes":["redis","scaling"],"type":"subscriber(n8n)","clusterNodes":[{"host":"node1","port":6379},{"host":"node1","port":6379}],"file":"redis-client.service.js","function":"createClusterClient"}
2025-08-05T09:32:39.720Z | error | [Redis client] Failed to refresh slots cache. {"scopes":["redis","scaling"],"error":{"lastNodeError":{}},"file":"redis-client.service.js"}
2025-08-05T09:32:39.730Z | error | [Redis client] Failed to refresh slots cache. {"scopes":["redis","scaling"],"error":{"lastNodeError":{}},"file":"redis-client.service.js"}

what am i missing? i was able to validate the elasticache cluster is accessible from the node where i am deploying redis and i was able to get the slots confiduration using redis cli from the same node.

Information on n8n setup

  • n8n version: 1.93.0
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): queuemode
  • Running n8n via (Docker, npm, n8n cloud, desktop app): kubernates
  • Operating system:

Hey @Prem_Sharma! I found this reported issue that could be related . I wonder if you could try by setting QUEUE_BULL_REDIS_HOST and QUEUE_BULL_REDIS_PORT just for test purposes?

Also I think that the key is in this thread

Basically there’s an opened PR to fix that error and be able to use Redis serverless!

Is that your case?

Happy to read your comments!

1 Like

this was it, thanks, i have moved to a non clustered redis for now, will follow the PR.

Awesome! Happy to help!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.