-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Bug Report: v19 tablet server config parsing incorrect #16392
Comments
Hi @shanth96! I believe this behavior change is coming from: #14733 Specifically here, as the value is an empty string after reading the empty config file: https://github.com/vitessio/vitess/pull/14733/files#diff-ee5ffc675b719e69de7147068ab4ecf03f6d5db91a000d212a30f8ce61544691R424-R431 That is still in place on main: vitess/go/vt/vttablet/tabletserver/tabletenv/config.go Lines 413 to 420 in 2e009e3
on main:
On v18:
|
Hi @mattlord! Thank you for the quick fix! |
Overview of the Issue
We're trying to validate v19 to upgrade our clusters and we noticed that Vitess is unable to boot up and gets stuck in a loop with the following errors:
While digging into this, we noticed that the errors were happening because
schemaChangeReloadTimeout
was being set to 0s (even though default is 30s and we don't explicitly configure it). This was causing the DEADLINE_EXCEEDED errors when trying to open the schema engine hereUpon further investigation, we noticed that the
initConfig
section of vttablet had some weird behaviour:Reproduction Steps
The code below is a simple reproduction of the
initConfig
code here.Running this in v18 vs v19 produces two different results:
where tablet-config.yaml is a simple yaml file with any config:
on v19, we get the following output:
vs. on v18, we get:
Particularly, note how schemaChangeReloadTimeout is not present as a config variable in v19 after unmarshaling.
Binary Version
Operating System and Environment details
Log Fragments
No response
The text was updated successfully, but these errors were encountered: