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

Some liveness checks don't actually check process #26574

Open
1 of 2 tasks
nsAstro opened this issue Sep 21, 2022 · 8 comments
Open
1 of 2 tasks

Some liveness checks don't actually check process #26574

nsAstro opened this issue Sep 21, 2022 · 8 comments
Labels

Comments

@nsAstro
Copy link
Contributor

nsAstro commented Sep 21, 2022

Description

Current liveness check probes use the 'airflow jobs' command which directly queries the backend DB as opposed to actually querying an endpoint or checking the status of the process itself.

e.g. Triggerer liveness probe

exec [sh -c CONNECTION_CHECK_MAX_COUNT=0 AIRFLOW__LOGGING__LOGGING_LEVEL=ERROR exec /entrypoint \
airflow jobs check --job-type TriggererJob --hostname $(hostname)] delay=10s timeout=20s period=60s #success=1 #failure=5

This command only checks the backend DB to see if there are any jobs. Additionally, the exit code is always 0 regardless of how many jobs there are. Ideally, the liveness check is done by querying some endpoint on the triggerer to see if it's still running.

Use case/motivation

Would like a liveness check that is more aware of the process rather than the stored state

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@nsAstro nsAstro added the kind:feature Feature Requests label Sep 21, 2022
@boring-cyborg
Copy link

boring-cyborg bot commented Sep 21, 2022

Thanks for opening your first issue here! Be sure to follow the issue template!

@potiuk
Copy link
Member

potiuk commented Sep 22, 2022

Marked it as good first issue, this is a good idea, and hopefully someone might improve it. BTW. @nsAstro - If you have ideas how to improve - you are most welcome to make PR #- this is an easy way to become one of the ~ 2200 contributors. Otherwise it will just have to wait for someone to pick it up.

@TruptiM18
Copy link

@potiuk, I would like to take this task. Can you please assign it to me?

@TruptiM18
Copy link

@potiuk, Can I take this task?

@TruptiM18
Copy link

TruptiM18 commented Oct 10, 2022

@uranusjr, Thanks! I have started working on it.

@amoghrajesh
Copy link
Contributor

@uranusjr @TruptiM18 if you aren't working on this, I would like to try my hand at it.
I see that the liveness checks can be improved for the scheduler and the triggerer here. Would like to hear what kind of liveness probe we would rather prefer. Calling an endpoint instead? Do we have ping for triggerer?

@uranusjr
Copy link
Member

Please feel free.

@amoghrajesh
Copy link
Contributor

Thanks. Any hints or clues on what we are looking to have as new liveness probes? @uranusjr

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

No branches or pull requests

5 participants