-
Notifications
You must be signed in to change notification settings - Fork 64
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
New Emqx gets OOMKilled immediately after deployment #1055
Comments
So strange, could you please check the failed pod and share it , just running |
I'm sorry, I have no idea. |
Regular docker image starts just fine with these limits
Perhaps there is a memory spike when operator applies config via API? Can we get core dump to see what exactly caused it? |
I am not sure how to take a core dump, if there are some commands that I can run, will replicate and send it. |
Looks emqx didn't print log to console, is there any way to print core dump log to console? @id Other, looks emqx didn't print any log, it's too strange |
Describe the bug
A clear and concise description of what the bug is.
I installed the cert-manager, then operator, then applied getting started yaml from docs.
The pods immediately fails saying OOMKilled, no logs.
I have tried other example deployment files, same issue with this file
Am I making some mistake ?
I have tried giving it more resources like this, but same issue
To Reproduce
Steps to reproduce the behavior:
Install operator using helm version : 2.2.23
And after wait to get conditions met from operator.
Then apply this
Expected behavior
The pods should run and cluster start
Anything else we need to know?:
enqx operator logs
Environment details::
The text was updated successfully, but these errors were encountered: