You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Additional context
after looking inside the health checks mounted from helm chart via config map at /health and running some tests, i found a solution:
instead of timeout -s 9 just use timeout -s 3 in following scripts:
because the kill signal for the timeout command is hard coded, please change it to 3 or replace it with an environment variable for more flexibility.
thx
The text was updated successfully, but these errors were encountered:
Which chart:
bitnami redis template version 9.0.2 and also 10.5.7
Describe the bug
on related docker nodes, you'll find redis-cli zombie processes:
those zombies seem to get caused from readiness / liveness health checks, when slave or master could not be reached within related timeout.
see also https://github.com/bitnami/bitnami-docker-redis/issues/165
To Reproduce
Steps to reproduce the behavior:
simulate connection problem by iptables DROP rule:
iptables -I INPUT -p tcp --dport 6379 -j DROP
login into redis-master or redis-slave container (pod) and execute health check:
Expected behavior
having no zombie processes on docker nodes after some days the docker redis service is running.
Version of Helm and Kubernetes:
helm version
:kubectl version
:Additional context
after looking inside the health checks mounted from helm chart via config map at
/health
and running some tests, i found a solution:instead of
timeout -s 9
just usetimeout -s 3
in following scripts:which are dynamic generated by https://github.com/bitnami/charts/blob/master/bitnami/redis/templates/health-configmap.yaml
when using kill signal 3 instead of 9, no zombie process will be spawned any more
because the kill signal for the
timeout
command is hard coded, please change it to 3 or replace it with an environment variable for more flexibility.thx
The text was updated successfully, but these errors were encountered: