-
Notifications
You must be signed in to change notification settings - Fork 102
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
keda-add-ons-http-external-scaler fatal error: concurrent map writes #414
Comments
thanks for this @morganchristiansson, I'll look into this as well. the trace helps greatly |
I encountered the same issue. I'm looking forward to see this issue fixed as it makes the addon unreliable. Thank you! |
@morganchristiansson @stefanbulzan #415 should fix this. |
@arschles I tested it with a locally build image from the fix branch. Looks good, doesn't fail anymore and scaling works. Brilliant! Thank you. I'm looking forward to have this in 0.4.0 hopefully. |
Yup, this will be in 0.4.0 for sure 👍 Thanks for testing it 😄 |
@stefanbulzan @morganchristiansson now that #415 is merged, you should see the fix in the |
Report
My keda-add-ons-http-external-scaler pod is crashlooping with
fatal error: concurrent map writes
error. See below for full output:I'll keep digging but thought it's worth reporting. May try reinstall again. Not sure what map it's referring to?
Sorry for long output I can move it to github gist instead? Or delete all except first goroutine trace?
Expected Behavior
Not crash
Actual Behavior
keda-add-ons-http-external-scaler is Crashlooping
Steps to Reproduce the Problem
Installed latest keda and http-add-on charts. No relevant custom values. Added some HTTPScaledObject resources. I've just switched to arm64 docker images for keda - but http-external-scaler was already crashlooping.
Logs from KEDA HTTP operator
No errors from keda http operator - only info and debug.
What version of the KEDA HTTP Addon are you running?
0.3.0
Kubernetes Version
1.21
Platform
Other
Anything else?
No response
The text was updated successfully, but these errors were encountered: