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

decrease cost of health check #9288

Merged
merged 1 commit into from
Jan 4, 2022
Merged

Conversation

jrhizor
Copy link
Contributor

@jrhizor jrhizor commented Jan 4, 2022

As far as I can tell, nobody actually needs to use the db value (HealthService just calls it and checks for an error and the scheduler app won't reach the point where the server is live if the db is not on startup).

@jrhizor jrhizor requested a review from davinchia January 4, 2022 17:53
@github-actions github-actions bot added area/api Related to the api area/documentation Improvements or additions to documentation area/frontend area/platform issues related to the platform area/scheduler area/server labels Jan 4, 2022
@jrhizor jrhizor temporarily deployed to more-secrets January 4, 2022 17:54 Inactive
@jrhizor jrhizor merged commit b475aa9 into master Jan 4, 2022
@jrhizor jrhizor deleted the jrhizor/cheaper-health-check branch January 4, 2022 18:07
@davinchia davinchia mentioned this pull request Apr 6, 2022
40 tasks
davinchia added a commit that referenced this pull request Apr 7, 2022
As part of digging into airbytehq/oncall#192. I realised the OSS Server's health checks aren't actually implemented. This was removed in ##9288. However we do require this to be implemented since we use it in Airbyte Cloud to inform whether the server is connected to the database or not and thus have properly start up.

Since this check can potentially be called multiple times a second, it is important for the check to be fast. Because of this, we check the server is working by attempting to list the id column of the workspace table's first row.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api Related to the api area/documentation Improvements or additions to documentation area/platform issues related to the platform area/scheduler area/server
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants