Redis Error blocking Execution list results


We are running our production environment for n8n with multiple redis clusters for reliability.

When trying to open the executions list via UI, we get the following error:

 "message":"CROSSSLOT Keys in request don't hash to the same slot",
 "stacktrace":"ReplyError: CROSSSLOT Keys in request don't hash to the same slot\n    
at parseError (/usr/local/lib/node_modules/n8n/node_modules/redis-parser/lib/parser.js:179:12)\n   
 at parseType (/usr/local/lib/node_modules/n8n/node_modules/redis-parser/lib/parser.js:302:14)"

Does N8N have an option to support Redis Cluster Mode?

Information on your n8n setup

  • n8n version: Latest
  • Database (default: SQLite): PostGres
  • n8n EXECUTIONS_PROCESS setting (default: own, main):Queue
  • Running n8n via (Docker, npm, n8n cloud, desktop app):Docker

Hi @pbirdie, I’m sorry you are having trouble. I don’t have access to a Redis cluster and the deployment seems considerably more complex than I hoped, but perhaps our local queue mode expert @krynble can chip in on this?

Hello @pbirdie

Thanks for reporting and sorry to hear you’re having trouble with that.

Our implementation of queue mode relies on an outdated version of the Bull library, which is not fully compatible with Redis Cluster.

It might work with a few workarounds, but it’s not as performant.

We have plans to upgrade to use BullMQ instead of Bull that would provide lots of improvements, including better interface with Redis Cluster.

Would it make sense for you to consider a regular Redis deployment?

1 Like

Redis Sentinel support would be amazing also - ✨ Add Redis Sentinel support by pemontto · Pull Request #5350 · n8n-io/n8n · GitHub

New version [email protected] got released which includes the GitHub PR 6708.

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