You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I look at individual worker stats, it displays stats about the whole node, instead of container one.
So e.g. I see Free Memory: 55.54GB / 62.81GB. Which is for whole node
To Reproduce
Go to Settings -> Workers
Look e.g. at Free Memory
Expected behavior
I expect to see actual Pod usage/limits.
Check cgroup v2
Operating System
Alpine Linux v3.19
n8n Version
1.39.1
Node.js Version
v18.19.1
Database
PostgreSQL
Execution mode
queue
The text was updated successfully, but these errors were encountered:
This is working as currently implemented. n8n Worker stats simply report the data that is available to the node.js process using the os module.
While it'd be great to get this data from cgroups v2, and then also use that to optimize the max heap-size, unfortunately this won't be doable until we drop support for node.js 18.
Bug Description
When I look at individual worker stats, it displays stats about the whole node, instead of container one.
So e.g. I see Free Memory: 55.54GB / 62.81GB. Which is for whole node
To Reproduce
Expected behavior
I expect to see actual Pod usage/limits.
Check cgroup v2
Operating System
Alpine Linux v3.19
n8n Version
1.39.1
Node.js Version
v18.19.1
Database
PostgreSQL
Execution mode
queue
The text was updated successfully, but these errors were encountered: