-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
100% CPU usage and keep posting event 'reset_instances' to go plugin server #12364
Comments
It is highly recommended to use the latest go-pdk version, currently We did some refactoring for this in 3.5. For details, please see: |
It's a fixed bug of 3.5. This line was missing in a refactoring PR and it's then added back. Please use the nightly build or wait for 3.6 release for this fix. |
Thank you for your prompt reply. The file you indicate is updated: |
You're right. They are missing in the same PR. |
This issue is marked as stale because it has been open for 14 days with no activity. |
May I know the expected release date of next version? |
@StarlightIbuki |
@StarlightIbuki I'll try to upgrade kong from 3.5 to 3.6 along with go-pdk 0.10 to see if this issue is fixed. |
… and Javascript plugin server crashes The bug was introduced when refactoring/cherry-picking. Fix #12364 Co-authored-by: Guilherme Salazar <gsz@acm.org>
@StarlightIbuki Sorry about the long call stack, I have try my best to reduce it.
|
The order of the traceback confuses me. |
The bug was introduced when refactoring/cherry-picking. Fix #12364 Co-authored-by: Guilherme Salazar <gsz@acm.org>
Is there an existing issue for this?
Kong version (
$ kong version
)Kong 3.5 / go-pdk 0.6.0
Current Behavior
There is a self-development plugin written by Go with go-pdk v0.6.0.
It is running well and stable more than one year.
Recently we've upgraded kong from 3.4.2 to 3.5.0 and then found sometimes 100% CPU usage happens and Kong keep calling
reset_instances
repeatedly but always failed.My key configuration to enable the Go plugin server:
When this issue happens, I noticed that:
After some quick tracing, it seems like this function https://github.com/Kong/kong/blob/3.5.0/kong/runloop/plugin_servers/mp_rpc.lua#L328-L345 is a recursive function and keep posting event
reset_instance
and call itself again if the error is stillno plugin instance
and then run out of event queue size.The most weirdest thing is that there is NO crash log related to the plugin but kong tries to reset it and then failed.
Also I found some similar issues:
#7148
#8293
#9301
cc @samugi @StarlightIbuki (not sure you guys are familiar with this issue)
Expected Behavior
Not making CPU 100% and restart the plugin server.
Steps To Reproduce
Not reproducible
Anything else?
No response
The text was updated successfully, but these errors were encountered: