Some workers with a CPU usage of 100%, and they are stuck in the loop of luajit.
davidwudv opened this issue · comments
David Wu commented
In our production environment, it is common to encounter situations where one or more workers have a CPU usage of 100%. I have tried using openresty-gdb-utils
and openresty-systemtap-toolkit
but cannot obtain the Lua stack trace, only the C stack trace. By examining the source code of luajit, it seems that it is stuck in a loop within the lj_gc_step
function shown in the screenshot.
We are using OpenResty version 1.13.6.2 and have attempted to update luajit separately, but the issue remains unresolved.
Could you please advise on how to solve this problem?
lijunlong commented
- OpenResty 1.13.6.2 is so old. You'd better update OpenResty to 1.21.4.
- You can use OpenResty Xray to analyze this issue.
David Wu commented
- OpenResty 1.13.6.2 is so old. You'd better update OpenResty to 1.21.4.
- You can use OpenResty Xray to analyze this issue.
Okay, thank you.