-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
[bitnami/rabbitmq] Fix high CPU usage while idle #11117
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @orgads Thanks a lot for your contribution.
I like this approach
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @orgads, sorry but there is a little failure in your PR. Could you have it a look?
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Fixes #11116 Signed-off-by: Orgad Shaneh <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! LGTM. Thanks a lot @orgads
https://www.rabbitmq.com/monitoring.html#deprecations this change implements a legacy health check. Shouldn't the default health check be one of the recommendations on the mentioned page above, instead of the legacy endpoint? |
The REST checks are not deprecated, only the liveness probe I used is. I preferred to use the deprecated version, because the current version requires vhost, which is %3f (/) by default, but I think can be customized. Would you prefer that? |
I think we can use |
Thanks @orgads. I agree with you about the CPU usage, but I think is better to keep aligned with RabbitMQ documentation, and report this kind of issues to the upstream project |
Apparently someone else already asked about this. They don't recommend using the CLI for probes. See here. |
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Fixes bitnami#11116 Signed-off-by: Orgad Shaneh <[email protected]> Signed-off-by: vaggeliskls <[email protected]>
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Fixes #11116 Signed-off-by: Orgad Shaneh <[email protected]>
* Revert "[bitnami/rabbitmq] Fix high CPU usage while idle (#11117)" This reverts commit 73966c6. Signed-off-by: Fran Mulero <[email protected]> * Version bump Signed-off-by: Fran Mulero <[email protected]> Signed-off-by: Fran Mulero <[email protected]>
* Revert "[bitnami/rabbitmq] Fix high CPU usage while idle (bitnami#11117)" This reverts commit 73966c6. Signed-off-by: Fran Mulero <[email protected]> * Version bump Signed-off-by: Fran Mulero <[email protected]> Signed-off-by: Fran Mulero <[email protected]>
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Reapply of bitnami#11117 and bitnami#11180. Fixes bitnami#11116. Signed-off-by: Orgad Shaneh <[email protected]> (cherry picked from commit 73966c6)
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Reapply of bitnami#11117 and bitnami#11180. Fixes bitnami#11116. Signed-off-by: Orgad Shaneh <[email protected]> (cherry picked from commit 73966c6)
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Reapply of #11117 and #11180. Fixes #11116. Signed-off-by: Orgad Shaneh <[email protected]> (cherry picked from commit 73966c6) Signed-off-by: Juan José Martos <[email protected]> Co-authored-by: Juan José Martos <[email protected]>
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Reapply of bitnami#11117 and bitnami#11180. Fixes bitnami#11116. Signed-off-by: Orgad Shaneh <[email protected]> (cherry picked from commit 73966c6) Signed-off-by: Juan José Martos <[email protected]> Co-authored-by: Juan José Martos <[email protected]>
Use REST APIs for liveness/readiness probes, instead of spawning expensive erlang processes. Reapply of #11117 and #11180. Fixes #11116. Signed-off-by: Orgad Shaneh <[email protected]> (cherry picked from commit 73966c6) Signed-off-by: Juan José Martos <[email protected]> Co-authored-by: Juan José Martos <[email protected]>
Description of the change
Use REST APIs for liveness/readiness probes, instead of spawning
expensive erlang processes.
Benefits
Negligible CPU usage.
Possible drawbacks
Applicable issues
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm