5 ms·

io_uring also caused a ton of problems for our containers in Kubernetes when Node 20 had enabled it by default. They scrambled and turned it off by default in h

by watt 2y ago

io_uring also caused a ton of problems for our containers in Kubernetes when Node 20 had enabled it by default. They scrambled and turned it off by default in https://github.com/nodejs/node/commit/686da19abb https://github.com/nodejs/node/commit/686da19abb

clhodapp 2y ago
That sounds like a dubious integration contract for initialization between libuv and node, not an issue with io_uring. I would assume the same thing would happen if they used traditional Posix APIs to open file handles before dropping their privileges.
sapiogram 2y ago
I'm extremely curious, what kinds of problems? We had entire Kubernetes nodes becoming unresponsive, and I think io_uring in Node 18.18.0 was responsible, but they had lots of stuff running on them so I was never able to pinpoint the exact cause.
- watt 2y ago
  We hit memory leaks. Containers keeling over getting OOM killed.
  - sapiogram 2y ago
    Ah okay, not the same symptoms as we had, then.
deleted 2y ago
[deleted]