-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
High CPU usage #7
Comments
Applied a CPU quota to mitigate this
|
Aaaah ya know, I just saw the tag that I was using from the example. I'll change it to your latest and close it if I don't notice it again. |
sfxworks
added a commit
to sfxworks/mc-router
that referenced
this issue
Mar 30, 2020
itzg#7 Deployed it with an older version. Works but ends up spiking in CPU usage. Easy to overlook. Also, for good measure/best practice, added resource request/limit.
itzg
pushed a commit
that referenced
this issue
Mar 30, 2020
* Update the image version in the example file #7 Deployed it with an older version. Works but ends up spiking in CPU usage. Easy to overlook. Also, for good measure/best practice, added resource request/limit. * Bad syntax on CPU limit value
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With barely any connections, spikes pretty high. Currently deployed as-is with the example servers replaced with my own. Happens with bungee, paper only, and vanilla with the service annotation. I don't see any major hits to the kube-api server, so it doesn't look like it's taxing that thankfully.
There is nothing abnormal in the logs of the mc-router pod.
Version info
Node types it was on:
The text was updated successfully, but these errors were encountered: