-
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] Revert rabbitmq probes #11177
Conversation
This reverts commit 73966c6. Signed-off-by: Fran Mulero <[email protected]>
Signed-off-by: Fran Mulero <[email protected]>
Please don't revert. I suggested using another API in a comment on my change. I can apply it tomorrow. |
Please accept #11180 instead of this. Using ~30% CPU constantly just for liveness/readiness probes does not make any sense. |
I agree with you at 100% about the CPU usage, but I think is better to keep aligned with RabbitMQ documentation. This problem should be reported to the upstream project |
I doubt they ever meant for these liveness checks to be executed every 20 seconds. I'll report anyway. |
* 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]>
Description of the change
This PR reverts changes in #11117 .Healthchecks implemented in that PR are deprecated
Benefits
Keep aligned with RabbitMQ Health Check recommendations
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