Skip to content
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

Add Health check capability to services #31

Open
rtisma opened this issue Nov 26, 2020 · 1 comment
Open

Add Health check capability to services #31

rtisma opened this issue Nov 26, 2020 · 1 comment
Assignees

Comments

@rtisma
Copy link
Contributor

rtisma commented Nov 26, 2020

Even though services are deployed with the restart=always docker parameter meaning when the service fails to boot (for instance, song-api wll not boot if it cannot create a connection to the song-db database), it restarts automatically.

Without this, the user will know that all services were successfully deploy, but will not know if they are healthy and ready to use. In the genomics data playground, readyness was manually checked on a per service basis by doing curl or docker exec commands.

With this feature, we can not only deploy song-api when the song-db is ready, but we can also block program exit until something exceeds the retry count or until everything succeeds.

This will require:

  • ability to query and process the state of a depoyment
  • retry the healthcheck with a back-off retry schedule, and report the failures
  • make healthchecking optional, with a switch (cli)
@rtisma rtisma self-assigned this Nov 26, 2020
@rtisma rtisma added this to the [FUTURE] Canarie Sprint 11 milestone Nov 26, 2020
@rtisma rtisma added the canarie label Nov 26, 2020
@b-f-chan
Copy link
Contributor

Testing scope - Only checks for EGO, but implementation is generic and can be applied to SONG, SCORE, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants