-
Notifications
You must be signed in to change notification settings - Fork 260
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
enable cpu limit for "robusta-forwarder" service as current config cause cpu hogging #1601
Comments
…ce as current config cause cpu hogging Signed-off-by: Pratik Raj <[email protected]>
Hi @Rajpratik71, there is nothing wrong with it consuming all the excess cpu on the node! We deliberately don't see limits in line with the approach here - https://home.robusta.dev/blog/stop-using-cpu-limits That said, if another pod is running on the same node and getting CPU throttled, you can fix it by increasing the CPU request for that other pod. |
@aantn Only In some scenarios it is good to remove limits to avoid throttling in applications. Otherwise , application without cpu limits will lead to a lot of issues like:
Same happened here, |
Hi @Rajpratik71 that's weird, it shouldn't consume 50cpu! That is a lot. Are you open to jumping on a call with our team to take a look? Regarding the limits, probably easier to discuss on a call too if you want to go more in depth. |
Describe the bug
Current helm config for
cpu limit
ofrobusta-forwarder
caused the pods to consume available cpu of the Node.To Reproduce
NA
Expected behavior
robusta-forwarder
pod should run in specified cpu limits.Screenshots
Environment Info (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: