Please consider this more as a question.
The docker container's health check is setup to call eturnalctl status once a minute and timout after 5 seconds.
I have just recently setup two instances of eturnal on docker, both of which take about 15 seconds to report status, hence being reported as unhealthy.
Comand run inside the container:
~ $ time eturnalctl status
eturnal is running
real 0m 15.10s
user 0m 0.03s
sys 0m 0.06s
The outcome is the same on AMD Epyc (~2.4GHz) and Intel Xeon (~2.1GHz) hosts, with next to no cpu usage in total.
I can fix this by adding custom healthcheck parameters in my docker-compose.yml so that's not an issue.
I do wonder though, if the discrepancy between the default 5 seconds and the experienced 15 seconds are a problem on my end, and if so, how to possibly debug and mitigate.
Best regards!
Please consider this more as a question.
The docker container's health check is setup to call
eturnalctl statusonce a minute and timout after 5 seconds.I have just recently setup two instances of eturnal on docker, both of which take about 15 seconds to report status, hence being reported as unhealthy.
Comand run inside the container:
The outcome is the same on AMD Epyc (~2.4GHz) and Intel Xeon (~2.1GHz) hosts, with next to no cpu usage in total.
I can fix this by adding custom
healthcheckparameters in mydocker-compose.ymlso that's not an issue.I do wonder though, if the discrepancy between the default 5 seconds and the experienced 15 seconds are a problem on my end, and if so, how to possibly debug and mitigate.
Best regards!