New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
K8s worker Stats #9288
Comments
This is working as currently implemented. n8n Worker stats simply report the data that is available to the node.js process using the 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. |
As this is not currently seen as a bug I am going to move this to closed for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: