docker containers reported as unhealthy due to slow eturnalctl status response

Open
#90 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, erlang
Domain
devops, networking

Research direction

Reproduce the reported delay by running eturnalctl status inside the Docker container and compare it with the five-second health-check timeout. Review the container health-check configuration and the docker-compose.yml override described in the issue; done means identifying the cause of the slow response and documenting or validating an appropriate health-check adjustment.

Written by the indexing model from the issue text.

Description

containers help wanted

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!

Dominant language
Erlang
Stars
342
Forks
25
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from processone/eturnal

All issues in processone/eturnal

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.