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

/healthz should not report ok when vttablet is not connected to mysql #8238

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

aquarapid
Copy link
Contributor

@aquarapid aquarapid commented Jun 2, 2021

When MySQLd is starting under vttablet control (e.g. when using -restore_from_backup),
as we do in the Vitess Operator, /healthz reports "ok" until mysqld is up, which is bad. Explicitly check for the
not connected state, and add tests for the /healthz handler.

Fixes #8237

Signed-off-by: Jacques Grove aquarapid@gmail.com

One issue here is that there may be existing operational flows that depend on this broken behavior.

-restore_from_backup), as we do in the Vitess Operator, /healthz
reports "ok" until MySQLd is up, which is bad.  Explicitly check for the
not connected state, and add tests for the /healthz handler.

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
@harshit-gangal harshit-gangal merged commit 5137052 into vitessio:main Jun 2, 2021
@harshit-gangal harshit-gangal deleted the jg_fixhealthz branch June 2, 2021 09:38
@deepthi deepthi changed the title When MySQLd is starting under vttablet control (e.g. when using /healthz should not report ok when vttablet is not connected to mysql Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

vttablet /healthz reports 200 / "ok" when not connected to MySQL yet
2 participants