Hey, I have one doubt about the environment variable N8N_RUNNERS_ENABLED:
In queue mode, my workers have their own sidecar container for task runners, so workers have N8N_RUNNERS_ENABLED=TRUE.
My main n8n instance have N8N_RUNNERS_ENABLED=FALSE and OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true, so that it doesn’t need to have its own side container for task runners. But with 2.0 n8n update, it seems that N8N_RUNNERS_ENABLED will forcibly be set to TRUE, does it means that even my main instance will need to have task runners?
Just to make it clear, this is the log I’m getting from my main n8n instance:
Initializing n8n process
n8n ready on ::, port 5678
There is a deprecation related to your environment variables. Please take the recommended actions to update your configuration:
- N8N_RUNNERS_ENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set `N8N_RUNNERS_ENABLED=true` to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/
[license SDK] Skipping renewal on init: license cert is not initialized
Version: 1.123.3
Start Active Workflows:
Activated workflow "My workflow" (ID: GllJn3NFfuDnMTcA)
Editor is now accessible via:
https://REDACTED
And this is the log I get from one of my workers:
n8n Task Broker ready on 0.0.0.0, port 5681
[license SDK] Skipping renewal on init: renewOnInit is disabled in config
[license SDK] Skipping renewal on init: autoRenewEnabled is disabled in config
[license SDK] Skipping renewal on init: license cert is not initialized
n8n worker is now ready
* Version: 1.123.3
* Concurrency: 10
Registered runner "launcher-python" (d1ca555fdf9d7bb6)
Registered runner "launcher-javascript" (efa90ffa01dda5b3)
This setup always worked for me, my workers are responsible for executing the jobs.
I’m getting this warning on the n8n 2.0 migration tool:
What does it mean? Is it telling me to add N8N_RUNNERS_ENABLED=TRUE on my main n8n instance?
I think you can set N8N_RUNNERS_ENABLED=true on your main instance just to satisfy the deprecation warning,
you already using OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true so i think you won’t need the task runner for the main instance.
Read this part from docs
I did it, but isn’t this going to waste resources on my main instance? Since I’m not going to be using the task runner from the main instance, it will be active unnecessarily.
Hi Carlos, I faced the same issue I will set them by pairs (Main + Runner , Each Worker with a Runner)
