Queue Mode binary data mode

Questions
1

I just saw this page in the documentation and found out that I’ve been running queue mode with binary data mode on filesystem for months. Now, the only issue I ever saw happening is that the binary data can’t self delete which is why I setup a cron job that goes through that binary data folder and deletes binary data older than 5 days (my executions clear out every 4 days)

It’s been working fine except that issue so is it recommended to switch to default mode?

Information on your n8n setup

  • n8n version: 1.63.4
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): no idea
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker
  • Operating system: N8N runs on Ubuntu
2

If the filesystem mode works for you, then please continue using it as you wish. We don’t recommend using it in queue mode because most of our customer deploying n8n in queue mode do so in a way that sharing a persistant volume is not possible between the various n8n containers.

3

Ahh yeah that makes sense. My workers are all on the same server. So you’re saying if im looking to change that, that’s when i’ll have to switch binary data mode correct?

4

as long as you can share volumes across containers, you can continue using the filesystem mode. There are storage drivers for various orchestrators that allow stuff like that across a cluster of servers.